You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Glen Mazza (JIRA)" <ji...@apache.org> on 2007/11/10 05:45:50 UTC
[jira] Created: (CXF-1196) @BindingType(SOAP11HTTP_MTOM_BINDING) is
not activating MTOM
@BindingType(SOAP11HTTP_MTOM_BINDING) is not activating MTOM
------------------------------------------------------------
Key: CXF-1196
URL: https://issues.apache.org/jira/browse/CXF-1196
Project: CXF
Issue Type: Bug
Affects Versions: 2.0.2
Reporter: Glen Mazza
Priority: Minor
The following attribute placed on the SEI implementation class will activate MTOM for GlassFish Metro but not for Apache CXF:
@BindingType(value=javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_MTOM_BINDING)
To confirm this, I used this class:
http://www.jroller.com/gmazza/date/20071102#NWSstep6
And the following additional tests:
1.) By removing/adding the above annotation, MTOM was turned off/on with Metro
2.) By adding the below to my cxf-servlet.xml config file, MTOM was turned on by CXF (i.e., so CXF can indeed do MTOM, it's just that the above annotation doesn't work.)
<jaxws:properties>
<entry key="mtom-enabled" value="true"/>
</jaxws:properties>
Page 130, bottom, of the WS 2.1 specification of May 2007 says that this binding (as well as SOAP12HTTP BINDING) should enable MTOM.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-1196) @BindingType(SOAP11HTTP_MTOM_BINDING)
is not activating MTOM
Posted by "Glen Mazza (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541532 ]
Glen Mazza commented on CXF-1196:
---------------------------------
No, actually it is even slightly deprecated in 2.1 (although still a part of it). It is on page 120 of the JAX-WS 2.0 standard of April 2006. This is a bug.
I would like to help out more in code but I still have more learning to do, so I can't emphasize coding as much right now. Just determining these errors takes a long time by itself.
> @BindingType(SOAP11HTTP_MTOM_BINDING) is not activating MTOM
> ------------------------------------------------------------
>
> Key: CXF-1196
> URL: https://issues.apache.org/jira/browse/CXF-1196
> Project: CXF
> Issue Type: Bug
> Affects Versions: 2.0.2
> Reporter: Glen Mazza
> Priority: Minor
>
> The following attribute placed on the SEI implementation class will activate MTOM for GlassFish Metro but not for Apache CXF:
> @BindingType(value=javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_MTOM_BINDING)
> To confirm this, I used this class:
> http://www.jroller.com/gmazza/date/20071102#NWSstep6
> And the following additional tests:
> 1.) By removing/adding the above annotation, MTOM was turned off/on with Metro
> 2.) By adding the below to my cxf-servlet.xml config file, MTOM was turned on by CXF (i.e., so CXF can indeed do MTOM, it's just that the above annotation doesn't work.)
> <jaxws:properties>
> <entry key="mtom-enabled" value="true"/>
> </jaxws:properties>
> Page 130, bottom, of the WS 2.1 specification of May 2007 says that this binding (as well as SOAP12HTTP BINDING) should enable MTOM.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CXF-1196) @BindingType(SOAP11HTTP_MTOM_BINDING)
is not activating MTOM
Posted by "maomaode (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
maomaode resolved CXF-1196.
---------------------------
Resolution: Fixed
Fix Version/s: 2.0.4
> @BindingType(SOAP11HTTP_MTOM_BINDING) is not activating MTOM
> ------------------------------------------------------------
>
> Key: CXF-1196
> URL: https://issues.apache.org/jira/browse/CXF-1196
> Project: CXF
> Issue Type: Bug
> Affects Versions: 2.0.2
> Reporter: Glen Mazza
> Assignee: maomaode
> Priority: Minor
> Fix For: 2.0.4
>
>
> The following attribute placed on the SEI implementation class will activate MTOM for GlassFish Metro but not for Apache CXF:
> @BindingType(value=javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_MTOM_BINDING)
> To confirm this, I used this class:
> http://www.jroller.com/gmazza/date/20071102#NWSstep6
> And the following additional tests:
> 1.) By removing/adding the above annotation, MTOM was turned off/on with Metro
> 2.) By adding the below to my cxf-servlet.xml config file, MTOM was turned on by CXF (i.e., so CXF can indeed do MTOM, it's just that the above annotation doesn't work.)
> <jaxws:properties>
> <entry key="mtom-enabled" value="true"/>
> </jaxws:properties>
> Page 130, bottom, of the WS 2.1 specification of May 2007 says that this binding (as well as SOAP12HTTP BINDING) should enable MTOM.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (CXF-1196) @BindingType(SOAP11HTTP_MTOM_BINDING)
is not activating MTOM
Posted by "maomaode (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
maomaode reassigned CXF-1196:
-----------------------------
Assignee: maomaode
> @BindingType(SOAP11HTTP_MTOM_BINDING) is not activating MTOM
> ------------------------------------------------------------
>
> Key: CXF-1196
> URL: https://issues.apache.org/jira/browse/CXF-1196
> Project: CXF
> Issue Type: Bug
> Affects Versions: 2.0.2
> Reporter: Glen Mazza
> Assignee: maomaode
> Priority: Minor
>
> The following attribute placed on the SEI implementation class will activate MTOM for GlassFish Metro but not for Apache CXF:
> @BindingType(value=javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_MTOM_BINDING)
> To confirm this, I used this class:
> http://www.jroller.com/gmazza/date/20071102#NWSstep6
> And the following additional tests:
> 1.) By removing/adding the above annotation, MTOM was turned off/on with Metro
> 2.) By adding the below to my cxf-servlet.xml config file, MTOM was turned on by CXF (i.e., so CXF can indeed do MTOM, it's just that the above annotation doesn't work.)
> <jaxws:properties>
> <entry key="mtom-enabled" value="true"/>
> </jaxws:properties>
> Page 130, bottom, of the WS 2.1 specification of May 2007 says that this binding (as well as SOAP12HTTP BINDING) should enable MTOM.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-1196) @BindingType(SOAP11HTTP_MTOM_BINDING)
is not activating MTOM
Posted by "maomaode (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541515 ]
maomaode commented on CXF-1196:
-------------------------------
Hi Glen,
Which version of Metro are you using? i guess it's 2.1.* , right?
This is actually jaxws 2.1 stuff, I have created the similar issue https://issues.apache.org/jira/browse/CXF-1142
We should link the two issues together
Wondering if you have interest to do this ;)
> @BindingType(SOAP11HTTP_MTOM_BINDING) is not activating MTOM
> ------------------------------------------------------------
>
> Key: CXF-1196
> URL: https://issues.apache.org/jira/browse/CXF-1196
> Project: CXF
> Issue Type: Bug
> Affects Versions: 2.0.2
> Reporter: Glen Mazza
> Priority: Minor
>
> The following attribute placed on the SEI implementation class will activate MTOM for GlassFish Metro but not for Apache CXF:
> @BindingType(value=javax.xml.ws.soap.SOAPBinding.SOAP11HTTP_MTOM_BINDING)
> To confirm this, I used this class:
> http://www.jroller.com/gmazza/date/20071102#NWSstep6
> And the following additional tests:
> 1.) By removing/adding the above annotation, MTOM was turned off/on with Metro
> 2.) By adding the below to my cxf-servlet.xml config file, MTOM was turned on by CXF (i.e., so CXF can indeed do MTOM, it's just that the above annotation doesn't work.)
> <jaxws:properties>
> <entry key="mtom-enabled" value="true"/>
> </jaxws:properties>
> Page 130, bottom, of the WS 2.1 specification of May 2007 says that this binding (as well as SOAP12HTTP BINDING) should enable MTOM.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.