Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
Java-SCA-1.5.1
-
None
-
All
Description
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