cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Glen Mazza (JIRA)" <>
Subject [jira] Commented: (CXF-927) jaxws:enableWrapperStyle apparently not working
Date Sat, 16 Feb 2008 13:11:09 GMT


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:
>             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 of the JAX-WS spec apparently does not
mandate wrapper style by default, but the enableWrapperStyle flag should still be able to
> [1]
> [2]
> [3] <portType name="AWSECommerceServicePortType">
>     <jaxws:bindings xmlns: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.

View raw message