The only simpleTypes that are currently supported are enumerations. We will add your request to our todo list.
Thanks, Rich Scheuerle XML & Web Services Development 512-838-5115 (IBM TL 678-5115) Russell Butek/Austin/IBM@ To: [EMAIL PROTECTED] IBMUS cc: Subject: Re: WSDL2Java and xsd:simpleTypes 02/05/2002 07:18 AM Please respond to axis-dev Which version of axis are you running? I just tried it this morning with a build from a couple days ago and it worked just fine. Russell Butek [EMAIL PROTECTED] David Altenburg <[EMAIL PROTECTED]> on 02/04/2002 06:31:08 PM Please respond to [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: WSDL2Java and xsd:simpleTypes We're currently having issues with the way that wsdl2java handles simple types that are not enumerations. Currently, a complex type defined as this: <xsd:complexType name="RootType"> <xsd:sequence> <xsd:element name="stringElem" type="xsd:string"/> <xsd:element name="enumElem" type="foo:enumType"/> <xsd:element name="simpleElem" type="foo:fooSimpleType"/> </xsd:sequence> </xsd:complexType> <xsd:simpleType name="fooSimpleType"> <restriction base="xsd:string"/> </xsd:simpleType> is translated into this: public class RootType implements java.io.Serializable { private FooSimpleType simpleElem; public RootType() { } public FooSimpleType getSimpleElem() { return simpleElem; } public void setSimpleElem(FooSimpleType simpleElem) { this.simpleElem = simpleElem; } } However, FooSimpleType is not generated, so the generated code does not compile. Is this a known issue, and if so, what is the planned fix? Would it be to replace all references to the simple type with references to the base type (or the first base type reached that maps to a java type when traversing the base types?) or to generate the class that is referenced (e.g. FooSimpleType)? Thanks, David Altenburg [EMAIL PROTECTED]