[
https://issues.jboss.org/browse/JBWS-3593?page=com.atlassian.jira.plugin....
]
Massimiliano Calipari commented on JBWS-3593:
---------------------------------------------
Hi Alessio,
I'm trying to apply your workaround to a WS while migrating it to JBoss EAP 6.2
Strangely the Interceptor is ignored and not loaded at all.
I tried both the @ OutInterceptors annotation and jbossws-cxf.xml configuration without
success.
Moreover, the jbossws-cxf.xml configuration set the MTOM processing to true on the same
end-point. The MTOM configuration works, the interceptor none.
{code:xml}
<jaxws:endpoint implementor="MyWS"
implementorClass="mypackage.MyWS">
<jaxws:outInterceptors>
<bean class="mypackage.cxf.MTOMOutInterceptor" />
</jaxws:outInterceptors>
<jaxws:properties>
<entry key="mtom-enabled" value="true"/>
</jaxws:properties>
</jaxws:endpoint>
{code}
What can be wrong?
multipart/related messages exchanged for @MTOM annotated endpoint
even if no attachment is included
---------------------------------------------------------------------------------------------------
Key: JBWS-3593
URL:
https://issues.jboss.org/browse/JBWS-3593
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-cxf, jbossws-native
Affects Versions: jbossws-cxf-4.0.2, jbossws-native-4.0.2
Environment: Jboss AS 7.1.1Final
Reporter: A l e c C R E S T A N
Assignee: Alessio Soldano
On JBoss AS 7.1.1, with the following service implementation:
{code}
@WebService(...)
@javax.xml.ws.BindingType (value=javax.xml.ws.soap.SOAPBinding.SOAP12HTTP_MTOM_BINDING)
public class SEIImpl {
...
public DataHandler getBin() {...} /* maps to a type="xs:base64Binary" in wsdl
*/
public List<String> getString(){...} /* maps to sequence of String in wsdl */
...
}
{code}
With the default *jbossws-cxf*, the responses are:
- for getString() method
Content-Type: multipart/related; type="application/xop+xml"; ...
- for getBin() method
Content-Type: multipart/related; type="application/xop+xml"; ...
-> +both responses are MTOM/XOP modified ! The getString() response should not.+
With *jbossws-native* (after the jbossws stack switching) , the responses are the
expected ones:
- for getString() method
Content-Type: text/xml;charset=UTF-8 <env:Envelope .... text content
..../env:Envelope>
- for getBin() method
Content-Type: multipart/related; type="application/xop+xml"; ...
Best regards,
Note: same behaviour with @javax.xml.ws.soap.MTOM or SOAP11HTTP_MTOM_BINDING
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira