Hi Thilina:
IMHO, it would be nicer if enable="true" did the behavior you describe
as "optional", and then we had a "require" value for always doing
MTOM/SwA (i.e. fault if a non-MTOM message received). The word "enable"
means "make possible", not "always do", so true/false/require makes more
sense to me. But +1 regardless.
So how do I control MTOM optimization when sending? If I'm in
"optional" mode, I assume there is some kind of runtime parameter that I
can set to say "MTOM-ize this particular message"? There are also some
heuristics that can be used here - for instance, if you're the server
and the client has indicated it accepts the MTOM media-type, you know
you can optimize if necessary.
Thanks,
--Glen
Thilina Gunarathne wrote:
Ooops... Hit the send accidentally...
Hi all,
In addition to the "true" and "false" values I introduced an
"optional" value to the enableMTOM and enableSwA configurations. When
enableMTOM configuration is set to "optional" and if the request
message is a MTOMized one, then Axis2 will respond using an MTOM
message . When enableSwA configuration is set to "optional" and if the
request is SwA, Axis2 will respond using an SwA message.
Following parameters can be set engine wide, service wise or operation
wise..
<parameter name="enableMTOM">optional</parameter>
<parameter name="enableSwA">optional</parameter>
I would like to make the above as the configuration of the default
axis2.xml..
thanks,
Thilina
--
Thilina Gunarathne - http://www.wso2.com - http://thilinag.blogspot.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
