I think you dont required to declare SomethingItemPropertyListInfo as complex element use simple element only
On Tue, Jul 14, 2009 at 4:21 AM, KARR, DAVID (ATTCINW) <[email protected]>wrote: > I'm using Axis 1.3. I have a schema with a complexType which has a > single sequence of one element (unbounded count on that one element). > It looks something like this (the commented element will come up later): > > <xs:complexType name="SomethingItemPropertyListInfo"> > <xs:sequence> > <xs:element name="PropertyData" > type="SomethingPropertyInfo" minOccurs="0" maxOccurs="unbounded"/> > <!--<xs:element name="Dummy" type="xs:boolean" > minOccurs="0"/> --> > </xs:sequence> > </xs:complexType> > > When we generate code from this schema, the generated class > corresponding to this type is, well, nonexistent. It generates nothing > for it. > > If we instead comment in the "Dummy" element, it generates the > "SomethingItemPropertyListInfo" class. This is a workaround, but an > annoying one. We'd really like to have the schema definition not > include "Dummy", but still generate the "SomethingItemPropertyListInfo" > type. > > At this point, we haven't attempted to inject Castor or XMLBeans into > the picture to customize our code generation. We would definitely > consider that if that's the only viable way to resolve this issue. > -- ******************************************** Yashvant Singh Chauhan Mobile- 09845277271 Bangalore *********************************************
