When generating code for anonymous nested simpleTypes within a complexType in a schema definition, I noticed that WSDL2Java generates <elementName>.java, <elementName>Type0.java so on. For example, If there is a complexType with name foo and another complex type with bar both these complex types declare an anonymous simpletype element with a name "baz". The WSDL2Java generates Baz.java and BazType0.java so on.. It just seems that nested classes seems like an obvious solution for this. I was wondering why WSDL2Java does not generate nested classes instead.
I also noticed that WSDL2Java generates a class even if all one does is add a pattern/length restriction - this seems very inefficient. Are there any plans to optimize/clean this up? Harish
