[
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.
