[ 
https://issues.apache.org/jira/browse/TUSCANY-3943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13124344#comment-13124344
 ] 

Scott Kurz commented on TUSCANY-3943:
-------------------------------------

After thinking some more I think Eric you've got the right idea as far as the 
wsdlgen, which is to simply map:

  @SOAPBinding(parameterStyle = SOAPBinding.ParameterStyle.BARE)

to:
     <jaxws:enableWrapperStyle>false</jaxws:enableWrapperStyle>

thereby enabling the new WSDL introspector logic to produce a match when 
interface compatibility is tested.

Let me just explain the case that falls through the cracks.    

1. Take a WSDL with  <jaxws:enableWrapperStyle>false</jaxws:enableWrapperStyle> 
and generate Java.
2. Later, take the generated Java with   @SOAPBinding(parameterStyle = 
SOAPBinding.ParameterStyle.BARE) and (re)generate a WSDL using a tool that does 
not gen the WSDL with the enableWrapperStyle set to 'false'.  
3. Package the new WSDL and Java in a Tuscany contribution and get an interface 
mismatch error.

I tried step 2 with wsgen and it did indeed fail to generate the WSDL with 
enableWrapperStyle set to 'false'.     (I wonder what CXF would do?)

I think this is a restriction that we can live with.   You'd either have to 
package the original WSDL or simply package no WSDL at all and let Tuscany 
generate one for you.

So the only thing left would be to fix the issue with scope/granularity of the 
reading of this customization in the WSDL (which I mentioned earlier) as well 
as the DOM namespace tweak I mentioned (and maybe fleshing out the 2nd test in 
this new itest?).

Eric, are you still interested in completing this?



                
> 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, 
> itest.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.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to