[
https://issues.apache.org/jira/browse/TUSCANY-3298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Nash resolved TUSCANY-3298.
---------------------------------
Resolution: Fixed
I haven't seen any problems as a result of these changes, so I'm marking this
issue as resolved, together with the related issues TUSCANY-3779 and
TUSCANY-3799.
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
