About Question enthuware.ocejws.v6.2.120 :

Moderators: Site Manager, fjwalraven

Post Reply
austinor
Posts: 41
Joined: Mon Oct 27, 2014 11:35 pm
Contact:

About Question enthuware.ocejws.v6.2.120 :

Post by austinor » Wed Nov 05, 2014 12:45 pm

Just curious: why the conditional in this statement:
"The <jaxws:enableWrapperStyle> declaration only affects operations that qualify for the wrapper style per the JAX-WS specification. ... wrapper style processing is turned on by default for all qualified operations"
... I mean, why the clause "only affects operations that qualify for the wrapper style...[OR] for all qualified operations"?

fjwalraven
Posts: 429
Joined: Tue Jul 24, 2012 2:43 am
Contact:

Re: About Question enthuware.ocejws.v6.2.120 :

Post by fjwalraven » Thu Nov 06, 2014 3:23 pm

Not all operations can be mapped in the wrapper style.
JAX-WS 2.2
2.3.1.2 Wrapper Style
A WSDL operation qualifies for wrapper style mapping only if the following criteria are met:
(i) The operation’s input and output messages (if present) each contain only a single part
(ii) The input message part refers to a global element declaration whose localname is equal to the operation name
(iii) The output message (if present) part refers to a global element declaration
(iv) The elements referred to by the input and output message (if present) parts (henceforth referred to as wrapper elements) are both complex types defined using the xsd:sequence compositor
(v) 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.

- Conformance (Default mapping mode): Operations that do not meet the criteria above MUST be mapped using non-wrapper style.
Regards,
Frits

austinor
Posts: 41
Joined: Mon Oct 27, 2014 11:35 pm
Contact:

Re: About Question enthuware.ocejws.v6.2.120 :

Post by austinor » Thu Nov 06, 2014 6:37 pm

fjwalraven wrote:Not all operations can be mapped in the wrapper style.
JAX-WS 2.2

2.3.1.2 Wrapper Style
A WSDL operation qualifies for wrapper style mapping only if the following criteria are met:

(i) The operation’s input and output messages (if present) each contain only a single part
(ii) The input message part refers to a global element declaration whose localname is equal to the operation name
(iii) The output message (if present) part refers to a global element declaration
(iv) The elements referred to by the input and output message (if present) parts (henceforth referred to as wrapper elements) are both complex types defined using the xsd:sequence compositor
(v) 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.

- Conformance (Default mapping mode): Operations that do not meet the criteria above MUST be mapped using non-wrapper style.
Regards,
Frits
Taking me a good deal of time to wrap my head around these points.

Post Reply

Who is online

Users browsing this forum: No registered users and 3 guests