[
https://issues.apache.org/jira/browse/CXF-5487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13875182#comment-13875182
]
Daniel Kulp commented on CXF-5487:
----------------------------------
I think we'd need a testcase for this. By default, mtom would likely be off
already. Thus, something would need to be turning it on. That something is
likely checked before anything set at the servlet level. For settings that
can be set in multiple places, there is an order of precedence and it's likely
that where ever it's setting it on is checked first. In anycase, a testcase
would be a big help.
> Disable MTOM from cxf-servlet.xml
> ---------------------------------
>
> Key: CXF-5487
> URL: https://issues.apache.org/jira/browse/CXF-5487
> Project: CXF
> Issue Type: Bug
> Components: Configuration, JAX-WS Runtime
> Affects Versions: 2.6.3, 2.6.11
> Environment: WebSphere 6.1, Apache Tomcat 7.0.47
> Reporter: Anna Baczulis
> Fix For: NeedMoreInfo
>
>
> I'm trying to disable MTOM through cxf-servlet.xml for one of the endpoints,
> but it has any effect to working Service.
> We have created Service with one void method annotated with WebMethod and two
> wrappers RequestWrapper and ResponseWrapper and RequestWrapper.
> Mentioned method has four attributes. Two first attributes are wrapped by
> ReuestWrapper and they are of type byte array and string, and next two are
> out-attributes and they are wrapped by are ResponseWrapper.
> Everyting works fine until I get response, becasue in response wrapper class,
> I have field of byte array (mentioned earlier). Which is automatically
> converted to XOP.
> This is very undesirable behavior in my business case (because of backward
> compatibility). I was trying to disable it using configuration file and
> <entry key="mtom-enabled" value="false" />.
> Which didn't change anything in runtime.
> Annotation @MTOM( enabled = false, threshold = 2048 ) did the thing, but it
> would be better if I could do the same from the configuration file level.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
