The problem with that is my service does not use the enums directly. It uses objects that access the enums, and I do not have the ability to change the interaction between the service objects and the enumerations. Any other suggestions?
On Tue, Jul 21, 2009 at 12:06 PM, robert lazarski <[email protected]>wrote: > On Tue, Jul 21, 2009 at 12:58 PM, Matt Schmidt<[email protected]> > wrote: > > Hello, > > I am having what appears to be a common problem, but everything I have > read > > says the issue should be resolved... > > I am using java2wsdl to generate a wsdl for my service, which contains > some > > enumerations. The resulting wsdl generates the enums incorrectly. (Java > 5, > > Axis2 1.4.1, Maven 2.0.9) > > <xs:complexType name="Status"> > > <xs:complexContent> > > <xs:extension base="xs:Enum"> > > <xs:sequence/> > > </xs:extension> > > </xs:complexContent> > > </xs:complexType> > > (Error: xs:Enum is not defined in 'http://www.w3.org/2001/XMLSchema') > > I am locked into Java 5. I have tried java2wsdl with Axis2 1.4.1 and 1.5, > > both with the same results. > > Everything I have read says that the issue was in Axis 1.3 and was > supposed > > to be fixed in the next version, but I still have the issue. > > Any suggestions or help? I am stuck... > > Thanks! > > > > > > As a quick hack and if you have control over the wsdl, one option is > use integer in the wsdl and Enum.ordinal() etc in your java code. > > - R >
