MTOM support in WSE 3.0



Hello,
As far as I understand, the WSE 3.0 provides some optimization of
MTOM usage. I.e. even if MTOM is specified,
but the size of data is less than 768 bytes, they are sent inline
instead of being referenced to XOP_INCLUDE.
For example, instead of

<data><Include> <href=... /> </Include></data>.

my WSE3.0- based client is sending

<data>VGhpcyBpcyBhIHNpbXBsZSB0ZXh0IGRvY3VtZW50Lg0KDQpZZXMgaXQgaXMu</
data>

I found an article which confirm this behavior
http://devauthority.com/blogs/area51/archive/2006/07/09/1534.aspx

The question is, can I somehow disable this optimisation? It creates
interoperatbility problems with my Java-based backend.

Thanks,
Nikolajs Krasnikovs

.