[
https://issues.apache.org/jira/browse/CXF-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489548
]
Chris Moesel commented on CXF-538:
----------------------------------
I'm not sure your example disqualifies it for wrapper style. The JAX-WS spec
2.3.1.2.v says this:
"The wrapper elements only contain child elements, they must not contain other
structures such as wildcards (element or attribute), xsd:choice, substitution
groups (element references are not permitted) or attributes; furthermore, they
must not be nillable."
Now, I'm not 100% sure on the terminology, but I consider a "child" to be a
direct descendant. So, in your example, the only child of the wrapper element
is the element named "port"-- and that element is not a wildcard (although it
contains wildcards itself).
Again, I'm not sure on this one, but thought I'd bring it up. I've found that
thus far, CXF is pretty good at sticking to the spec (and have confirmed that
if you use a wildcard as a direct descendant of the wrapper, it does generate
it using BARE style).
> if element include wildcards such as xs:any, according to jaxws specs, should
> not generated code using wrapper style
> --------------------------------------------------------------------------------------------------------------------
>
> Key: CXF-538
> URL: https://issues.apache.org/jira/browse/CXF-538
> Project: CXF
> Issue Type: Bug
> Reporter: Freeman Fang
>
> <element name="sayHi">
> <xs:complexType>
> <xs:sequence>
> <xs:element name="port" minOccurs="0"
> maxOccurs="unbounded">
> <xs:complexType>
> <xs:sequence>
> <xs:any namespace="##other"
> processContents="lax"><!-- minOccurs="0" maxOccurs="unbounded"-->
> </xs:any>
> <!--element name="requestType"
> type="string"/-->
> </xs:sequence>
> </xs:complexType>
> </xs:element>
> </xs:sequence>
> </xs:complexType>
> </element>
> this element include xs:any, which is a kind of wildcard, according to
> jaxws-specs, shouldn't generate code using wrapper style
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
