[jira] Assigned: (TUSCANY-2505) Problem in case: start with DLW wsdl, generate Java w/ wsimport, throw away WSDL and use , when wrapper elem used named type (not anonymous)

["Raymond Feng (JIRA)" <de...@tuscany.apache.org>]

     [ https://issues.apache.org/jira/browse/TUSCANY-2505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Raymond Feng reassigned TUSCANY-2505:
-------------------------------------

    Assignee: Raymond Feng

> Problem in case: start with DLW wsdl, generate Java w/ wsimport, throw away WSDL and use <intf.java>, when wrapper elem used named type (not anonymous)
> -------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TUSCANY-2505
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-2505
>             Project: Tuscany
>          Issue Type: Bug
>          Components: Java SCA Data Binding Runtime
>            Reporter: Scott Kurz
>            Assignee: Raymond Feng
>            Priority: Minor
>         Attachments: 2505.maybe.another.approach.is.better.patch
>
>
> In the case I mentioned, the JAXWSJavaInterfaceProcessor.visitInterface will introspect the wrapper bean class and do a:
>   inputWrapperDT.getLogical().getElementName();
> to get the wrapper element name.     
> This would work fine if the wrapper bean class were not present, since we provide a default for the generated wrapper.  It also works fine
> if the wrapper class is present when the wrapper element is of an anonymous type, since the wrapper class will have the @XmlRootElement
> annotation.  
> In the case I mentioned, though, the introspection of the wrapper bean will set up a DataType with a null element name.
> Later, in the runtime wsdlgen function, this will be a problem, and we will have a failure because of this null elem name.
> I'm attaching a fix which does the introspection anyway, and if the introspected DT has a null elem name, we'll use the one from the @RequestWrapper.
> That said, I don't understand why we would even need to go through this introspection if we have a complete @RequestWrapper or @ResponseWrapper on the Java method.       
> So maybe someone who understands this more completely could add to this. 
> Thanks,
> Scott

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.