Yes, it will. Using any XML data binding tool with a WS framework (Axis 1.x, Axis 2.x, XFire, Spring-WS come to my mind) should not only eliminate problems on the WS generation side of things, but make things more manageable in general, as you are separating WS operations (and their semantics) from the payload and its handling.
Regards Werner KARR, DAVID (ATTCINW) wrote: > I'm currently using Axis 1.3 (sorry, upgrading is not a choice right > now) without a separate code generator, like Castor. > > I have a schema with a complexType that only has a single unbounded > element in a sequence. It looks something like this: > > <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 I run WSDL2Java on the wsdl that references this schema, it doesn't > generate the "SomethingItemPropertyListInfo" class. If I instead remove > the comment characters surrounding the "Dummy" element and then > regenerate, it does generate the class. > > When I turned on debug output for WSDL2Java, it proved to me (which I > thought) that Axis assumes that it doesn't need to generate > "SomethingItemPropertyListInfo", but it instead uses > "SomethingPropertyInfo[]" wherever "SomethingItemPropertyListInfo" was > referenced. In this case, it's being too smart for me, because I really > want to have that class generated. > > I've considered plugging Castor into this instead of using the Axis code > generator. Will Castor help me solve this problem, without creating too > many new problems? > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
