You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Simon Nash (JIRA)" <de...@tuscany.apache.org> on 2010/12/02 13:02:11 UTC

[jira] Reopened: (TUSCANY-3298) Tuscany generated wrappers are not correct in all situations

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

Simon Nash reopened TUSCANY-3298:
---------------------------------

      Assignee: Simon Nash

Although this was closed and marked as fixed, I don't see any code changes for it.  The WSDL generation code is currently generating theTuscany wrappers.

I think it's important to make the change to using the JAXB wrappers because this should fix a number of WSDL generation problems including TUSCANY-3779 and TUSCANY-3799.

I've been looking into this and I have fixes that seem to produce a clean build with all tests passing except for the problem being tracked under TUSCANY-3805.

I'm therefore reopening this issue and I'll add further updates here about the code changes needed to get the JAXB wrappers fully working.

> Tuscany generated wrappers are not correct in all situations
> ------------------------------------------------------------
>
>                 Key: TUSCANY-3298
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-3298
>             Project: Tuscany
>          Issue Type: Bug
>          Components: Java SCA Axis Binding Extension
>    Affects Versions: Java-SCA-1.5.1
>         Environment: All
>            Reporter: Simon Laws
>            Assignee: Simon Nash
>             Fix For: Java-SCA-1.x
>
>
> While fixing TUSCANY3283 I noticed and interesting effect of generating wrapper schema ourselves rather than letting JAXB do it. From itest/wsdlgen, for the type...
> @XmlType(name="")
> public class CBean { 
> }
> Our wrapper generation code produces 
> <xs:element name="getGreetingsCBean">
>   <xs:complexType>
>     <xs:sequence>
>       <xs:element minOccurs="0" name="arg0" nillable="true" type=""/>
>     </xs:sequence>
>   </xs:complexType>
> </xs:element>
> I assume this is because the wrapper has no type name to play with. This is easily fixed by getting JAXB to generate the wrappers for us, in which case the structure for CBean is generated in line. However the downside of this change is that some tests in the build fail. See this discussion... 
> http://www.mail-archive.com/dev%40tuscany.apache.org/msg10002.html

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