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/08/21 06:37:31 UTC
[jira] Created: (CXF-927) jaxws:enableWrapperStyle not working for
Amazon ECS WSDL
jaxws:enableWrapperStyle not working for Amazon ECS WSDL
--------------------------------------------------------
Key: CXF-927
URL: https://issues.apache.org/jira/browse/CXF-927
Project: CXF
Issue Type: Bug
Components: Tooling
Affects Versions: 2.0.1
Reporter: Glen Mazza
Priority: Minor
jaxws:enableWrapperStyle is working for Metro but not CXF for the Amazon E Commerce Service[1]'s WSDL[2]. CXF's output is always in non-wrapped format (ParameterStyle.BARE) when generated by CXF. For Metro, this WSDL is in wrapper style by default. (It is apparently OK that CXF defaults to non-wrapped, because Section 2.3.1.2 of the JAX-WS spec apparently does not mandate wrapper style by default, but the enableWrapperStyle flag should still be able to work.)
[1] http://www.amazon.com/E-Commerce-Service-AWS-home-page/b?ie=UTF8&node=12738641
[2] http://webservices.amazon.com/AWSECommerceService/AWSECommerceService.wsdl?
[3] <portType name="AWSECommerceServicePortType">
<jaxws:bindings xmlns:jaxws="http://java.sun.com/xml/ns/jaxws">
<jaxws:enableWrapperStyle>false</jaxws:enableWrapperStyle>
</jaxws:bindings>
....
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-927) jaxws:enableWrapperStyle apparently not
working
Posted by "Glen Mazza (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569551#action_12569551 ]
Glen Mazza commented on CXF-927:
--------------------------------
Either this has been fixed by version 2.0.4, or there was actually nothing wrong with enableWrapperStyle with a WSDL file to begin with. I was confused between the meaning of wrapper and non-wrapper styles as defined in the JAX-WS spec (Figure 2.2 and text just before that), as it seems counterintuitive. Wrapper style actually means the individual elements of the input message become separate Java parameters in the SEI; non-wrapper style means the Java object representing the entire input message is used as the lone parameter.
> jaxws:enableWrapperStyle apparently not working
> -----------------------------------------------
>
> Key: CXF-927
> URL: https://issues.apache.org/jira/browse/CXF-927
> Project: CXF
> Issue Type: Bug
> Components: Tooling
> Affects Versions: 2.0.1
> Reporter: Glen Mazza
> Priority: Minor
>
> jaxws:enableWrapperStyle is working for Metro but not CXF for the Amazon E Commerce Service[1]'s WSDL[2]. CXF's output is always in non-wrapped format (ParameterStyle.BARE) when generated by CXF. For Metro, this WSDL is in wrapper style by default. (It is apparently OK that CXF defaults to non-wrapped, because Section 2.3.1.2 of the JAX-WS spec apparently does not mandate wrapper style by default, but the enableWrapperStyle flag should still be able to work.)
> [1] http://www.amazon.com/E-Commerce-Service-AWS-home-page/b?ie=UTF8&node=12738641
> [2] http://webservices.amazon.com/AWSECommerceService/AWSECommerceService.wsdl?
> [3] <portType name="AWSECommerceServicePortType">
> <jaxws:bindings xmlns:jaxws="http://java.sun.com/xml/ns/jaxws">
> <jaxws:enableWrapperStyle>false</jaxws:enableWrapperStyle>
> </jaxws:bindings>
> ....
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CXF-927) jaxws:enableWrapperStyle apparently not
working
Posted by "Glen Mazza (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Glen Mazza resolved CXF-927.
----------------------------
Resolution: Invalid
> jaxws:enableWrapperStyle apparently not working
> -----------------------------------------------
>
> Key: CXF-927
> URL: https://issues.apache.org/jira/browse/CXF-927
> Project: CXF
> Issue Type: Bug
> Components: Tooling
> Affects Versions: 2.0.1
> Reporter: Glen Mazza
> Priority: Minor
>
> jaxws:enableWrapperStyle is working for Metro but not CXF for the Amazon E Commerce Service[1]'s WSDL[2]. CXF's output is always in non-wrapped format (ParameterStyle.BARE) when generated by CXF. For Metro, this WSDL is in wrapper style by default. (It is apparently OK that CXF defaults to non-wrapped, because Section 2.3.1.2 of the JAX-WS spec apparently does not mandate wrapper style by default, but the enableWrapperStyle flag should still be able to work.)
> [1] http://www.amazon.com/E-Commerce-Service-AWS-home-page/b?ie=UTF8&node=12738641
> [2] http://webservices.amazon.com/AWSECommerceService/AWSECommerceService.wsdl?
> [3] <portType name="AWSECommerceServicePortType">
> <jaxws:bindings xmlns:jaxws="http://java.sun.com/xml/ns/jaxws">
> <jaxws:enableWrapperStyle>false</jaxws:enableWrapperStyle>
> </jaxws:bindings>
> ....
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (CXF-927) jaxws:enableWrapperStyle apparently not
working
Posted by "Glen Mazza (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Glen Mazza closed CXF-927.
--------------------------
Assignee: Glen Mazza
> jaxws:enableWrapperStyle apparently not working
> -----------------------------------------------
>
> Key: CXF-927
> URL: https://issues.apache.org/jira/browse/CXF-927
> Project: CXF
> Issue Type: Bug
> Components: Tooling
> Affects Versions: 2.0.1
> Reporter: Glen Mazza
> Assignee: Glen Mazza
> Priority: Minor
>
> jaxws:enableWrapperStyle is working for Metro but not CXF for the Amazon E Commerce Service[1]'s WSDL[2]. CXF's output is always in non-wrapped format (ParameterStyle.BARE) when generated by CXF. For Metro, this WSDL is in wrapper style by default. (It is apparently OK that CXF defaults to non-wrapped, because Section 2.3.1.2 of the JAX-WS spec apparently does not mandate wrapper style by default, but the enableWrapperStyle flag should still be able to work.)
> [1] http://www.amazon.com/E-Commerce-Service-AWS-home-page/b?ie=UTF8&node=12738641
> [2] http://webservices.amazon.com/AWSECommerceService/AWSECommerceService.wsdl?
> [3] <portType name="AWSECommerceServicePortType">
> <jaxws:bindings xmlns:jaxws="http://java.sun.com/xml/ns/jaxws">
> <jaxws:enableWrapperStyle>false</jaxws:enableWrapperStyle>
> </jaxws:bindings>
> ....
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Commented: (CXF-927) jaxws:enableWrapperStyle apparently
not working
Posted by Glen Mazza <gl...@verizon.net>.
Thanks! I'll look at this next.
Glen
Am Samstag, den 29.09.2007, 19:23 -0700 schrieb maomaode (JIRA):
> [ https://issues.apache.org/jira/browse/CXF-927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531288 ]
>
> maomaode commented on CXF-927:
> ------------------------------
>
> * cxf/tools/wsdlto/frontend/jaxws/src/main/java/org/apache/cxf/tools/wsdlto/frontend/jaxws/customization/CustomizationParser.java
> This is class is used to parse the binding file, and will merge the bindinding file as embedded customization rules into the wsdl. check if the enableWrapperStyle is set there
>
> The customization is done after the wsdlDefinition is built , see
>
> * tools/wsdlto/core/src/main/java/org/apache/cxf/tools/wsdlto/WSDLToJavaContainer.java
>
> The customized definition will be a input to the ServiceBuilder, which build the CXF wsdlModel, which will pass in to a processor chain which generate the artifacts.
>
> You probably should look at the
> * rt/core/src/main/java/org/apache/cxf/wsdl11/WSDLServiceBuilder.java, the build determine if the parameter style is in bare or wrapped, just make sure the enableWrappedStyle is passed to this builder.
>
>
>
>
> > jaxws:enableWrapperStyle apparently not working
> > -----------------------------------------------
> >
> > Key: CXF-927
> > URL: https://issues.apache.org/jira/browse/CXF-927
> > Project: CXF
> > Issue Type: Bug
> > Components: Tooling
> > Affects Versions: 2.0.1
> > Reporter: Glen Mazza
> > Priority: Minor
> >
> > jaxws:enableWrapperStyle is working for Metro but not CXF for the Amazon E Commerce Service[1]'s WSDL[2]. CXF's output is always in non-wrapped format (ParameterStyle.BARE) when generated by CXF. For Metro, this WSDL is in wrapper style by default. (It is apparently OK that CXF defaults to non-wrapped, because Section 2.3.1.2 of the JAX-WS spec apparently does not mandate wrapper style by default, but the enableWrapperStyle flag should still be able to work.)
> > [1] http://www.amazon.com/E-Commerce-Service-AWS-home-page/b?ie=UTF8&node=12738641
> > [2] http://webservices.amazon.com/AWSECommerceService/AWSECommerceService.wsdl?
> > [3] <portType name="AWSECommerceServicePortType">
> > <jaxws:bindings xmlns:jaxws="http://java.sun.com/xml/ns/jaxws">
> > <jaxws:enableWrapperStyle>false</jaxws:enableWrapperStyle>
> > </jaxws:bindings>
> > ....
>
[jira] Commented: (CXF-927) jaxws:enableWrapperStyle apparently not
working
Posted by "maomaode (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531288 ]
maomaode commented on CXF-927:
------------------------------
* cxf/tools/wsdlto/frontend/jaxws/src/main/java/org/apache/cxf/tools/wsdlto/frontend/jaxws/customization/CustomizationParser.java
This is class is used to parse the binding file, and will merge the bindinding file as embedded customization rules into the wsdl. check if the enableWrapperStyle is set there
The customization is done after the wsdlDefinition is built , see
* tools/wsdlto/core/src/main/java/org/apache/cxf/tools/wsdlto/WSDLToJavaContainer.java
The customized definition will be a input to the ServiceBuilder, which build the CXF wsdlModel, which will pass in to a processor chain which generate the artifacts.
You probably should look at the
* rt/core/src/main/java/org/apache/cxf/wsdl11/WSDLServiceBuilder.java, the build determine if the parameter style is in bare or wrapped, just make sure the enableWrappedStyle is passed to this builder.
> jaxws:enableWrapperStyle apparently not working
> -----------------------------------------------
>
> Key: CXF-927
> URL: https://issues.apache.org/jira/browse/CXF-927
> Project: CXF
> Issue Type: Bug
> Components: Tooling
> Affects Versions: 2.0.1
> Reporter: Glen Mazza
> Priority: Minor
>
> jaxws:enableWrapperStyle is working for Metro but not CXF for the Amazon E Commerce Service[1]'s WSDL[2]. CXF's output is always in non-wrapped format (ParameterStyle.BARE) when generated by CXF. For Metro, this WSDL is in wrapper style by default. (It is apparently OK that CXF defaults to non-wrapped, because Section 2.3.1.2 of the JAX-WS spec apparently does not mandate wrapper style by default, but the enableWrapperStyle flag should still be able to work.)
> [1] http://www.amazon.com/E-Commerce-Service-AWS-home-page/b?ie=UTF8&node=12738641
> [2] http://webservices.amazon.com/AWSECommerceService/AWSECommerceService.wsdl?
> [3] <portType name="AWSECommerceServicePortType">
> <jaxws:bindings xmlns:jaxws="http://java.sun.com/xml/ns/jaxws">
> <jaxws:enableWrapperStyle>false</jaxws:enableWrapperStyle>
> </jaxws:bindings>
> ....
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CXF-927) jaxws:enableWrapperStyle apparently not
working
Posted by "Glen Mazza (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Glen Mazza updated CXF-927:
---------------------------
Summary: jaxws:enableWrapperStyle apparently not working (was: jaxws:enableWrapperStyle not working for Amazon ECS WSDL)
Team,
Apparently another user[1, search on "Glen Mazza"] has also incurred this problem. If I wanted to fix this issue, in which classes would I need to look?
Thanks,
Glen
[1] http://blog.pulleman.com/2007/09/06/apache-cxf-and-glassfish-metro-for-consuming-web-services/
> jaxws:enableWrapperStyle apparently not working
> -----------------------------------------------
>
> Key: CXF-927
> URL: https://issues.apache.org/jira/browse/CXF-927
> Project: CXF
> Issue Type: Bug
> Components: Tooling
> Affects Versions: 2.0.1
> Reporter: Glen Mazza
> Priority: Minor
>
> jaxws:enableWrapperStyle is working for Metro but not CXF for the Amazon E Commerce Service[1]'s WSDL[2]. CXF's output is always in non-wrapped format (ParameterStyle.BARE) when generated by CXF. For Metro, this WSDL is in wrapper style by default. (It is apparently OK that CXF defaults to non-wrapped, because Section 2.3.1.2 of the JAX-WS spec apparently does not mandate wrapper style by default, but the enableWrapperStyle flag should still be able to work.)
> [1] http://www.amazon.com/E-Commerce-Service-AWS-home-page/b?ie=UTF8&node=12738641
> [2] http://webservices.amazon.com/AWSECommerceService/AWSECommerceService.wsdl?
> [3] <portType name="AWSECommerceServicePortType">
> <jaxws:bindings xmlns:jaxws="http://java.sun.com/xml/ns/jaxws">
> <jaxws:enableWrapperStyle>false</jaxws:enableWrapperStyle>
> </jaxws:bindings>
> ....
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.