Hi,
after verification of the behavior I filed a JIRA (AXIS2-3340).
Thanks again,
-Rainer
Thilina Gunarathne wrote:
Hi,
When the flag is set to optional and the request message is a
MTOMized one, then the system is expected to work as MTOM was enabled.
Does the optional work for non-fault
Hi,
When the flag is set to optional and the request message is a
MTOMized one, then the system is expected to work as MTOM was enabled.
Does the optional work for non-fault cases.. Please log a jira if
it is not working even for the non-fault scenarios.
Not sure what is going wrong.. I'll do
Hi,
Thilina Gunarathne wrote:
Hi,
Thilina recently helped me out on how to enforce the output encoding to
be MTOM if input is also MTOM, using this kind of code:
This is little bit more easy with the 1.3 release.. You can change the
enableMTOM parameter as follows to get the
Hi,
Microsoft WSE3 requires that MTOM is to be used either not at all or for
every message involved in a request (the reasoning behind this can
questioned ...). So in order to work with WSE3 and MTOM, WSE3 expects
all input-, output- and possible error message as MTOM encoded message.
Hi,
Thilina recently helped me out on how to enforce the output encoding to
be MTOM if input is also MTOM, using this kind of code:
This is little bit more easy with the 1.3 release.. You can change the
enableMTOM parameter as follows to get the behaviour you wanted..
parameter
