[
https://issues.apache.org/jira/browse/TUSCANY-3943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13100419#comment-13100419
]
Eric Larsen commented on TUSCANY-3943:
--------------------------------------
I have implemented a simple tag model which handles the
jaxws:enableWrappedStyle tag, and then uses the model extension in the wrapper
logic.
In addition to the WSDL processing side, a modification was needed for the Java
-> WSDL logic due to contract matching. All non-wrapped operations now output
a jaxws:elementWrappedStyle false tag, since you cannot distinguish between
non-wrapped and disable-wrapped cases at that point, and adding the tag does
not impact the non-wrapped logic.
> JAXWS Elements are not processed by the WSDLModelResolver -
> enableWrapperStyle elements are ignored
> ---------------------------------------------------------------------------------------------------
>
> Key: TUSCANY-3943
> URL: https://issues.apache.org/jira/browse/TUSCANY-3943
> Project: Tuscany
> Issue Type: Improvement
> Components: SCA Java Runtime
> Environment: All systems
> Reporter: Eric Larsen
> Fix For: Java-SCA-2.x
>
> Attachments: binding-ws-wsdlgen.patch, interface-wsdl.patch
>
>
> Tuscany doesn't process any jaxws tags that are included in WSDL files. This
> causes any enableWrapperStyle elements to be ignored, which causes a logic
> failure in the wrapping logic when Tuscany expects wrapped objects, and Java
> classes generated by external tools such as wsimport are not wrapped.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
