About Question enthuware.ocejws.v6.2.157 :

Moderators: Site Manager, fjwalraven

fjwalraven
Posts: 423
Joined: Tue Jul 24, 2012 2:43 am
Contact:

Re: About Question enthuware.ocejws.v6.2.157 :

Post by fjwalraven » Wed Nov 23, 2016 12:25 pm

Good question!

You can define different thresholds on client and server. Let's say that the client has a threshold of 0 and the server has a threshold of 100. If you send a text message of 50 bytes from client to server and back. The message from client to server is sent as an attachment and from server to client inline.

The answer to your question: no they don't interfere.

Regards,
Frits

johnlong
Posts: 185
Joined: Mon Jun 20, 2016 5:06 pm
Contact:

Re: About Question enthuware.ocejws.v6.2.157 :

Post by johnlong » Fri Nov 25, 2016 1:01 pm

Is default threshold 0 or 1Kb?

https://jax-ws.java.net/2.2.1/docs/mtom-swaref.html
As defined by JAXB 2.0 specification xs:base64Binary and xs:hexBinary mapping to java is byte[]. JAX-WS implementation has set a threshold of 1KB of byte[] size.
Default threshold value for MTOM feature is 0 bytes.

fjwalraven
Posts: 423
Joined: Tue Jul 24, 2012 2:43 am
Contact:

Re: About Question enthuware.ocejws.v6.2.157 :

Post by fjwalraven » Fri Nov 25, 2016 1:21 pm

Follow the specs (JAX-WS 2.2) in this case:
6.5.2 javax.xml.ws.soap.MTOMFeature
The MTOMFeature has one property threshold, that can be configured to serve as a hint for which binary
data SHOULD be sent as an attachment. The threshold is the size in bytes that binary data SHOULD be
in order to be sent as an attachment. The threshold MUST not be negative. The default value is 0.
Regards,
Frits

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest