Losing complex type info upon deploying wsdl

[a4rahman]

Hello,

I have a web service that has a web method that:

1. Takes a complex type (among other String parameters) as input

2. Returns a different complex type

When I generate the wsdl locally, it shows me the complex types and their details as follows:

<complexType name="TheInputTypeName">
    <sequence>
     <element name="parameterOneInInputType" nillable="true" type="xsd:base64Binary"/>
     <element name="parameterTwoInInputType" nillable="true" type="xsd:string"/>
    </sequence>
   </complexType>
   <complexType name="TheReturnTypeName">
    <sequence>
     <element name="parameterOneInReturnType" type="xsd:anyType"/>
     <element name="ParameterTwoInReturnType" nillable="true" type="xsd:base64Binary"/>
    </sequence>
</complexType>

However, when I use the JBoss Maven plugin to deploy this to my JBoss server, all I get for each of those complex types in my deployed wsdl is:

<xs:complexType name="nameOfType">
    <xs:sequence/>
</xs:complexType>

i.e., no definition of what's actually in the class, like I do in my local wsdl.

Is there a fix? Any way to maybe annotate my classes corresponding to the complex types in question, so that I can see the parameters within them in my wsdl? I looked into JAX-WS annotations but couldn't find anything useful, which is understandable because my complex types are just classes that I wrote and have nothing to do with web services.

Thanks in advance.

[a4rahman]

Ok, so I was able to solve part of the problem by using JAXB annotations in my class. I can now generate the xml elements corresponding to my getters.

But how do I annotate the non-default constructor?

[a4rahman]

Blah...solved it by just annotating my getters and introducing setters to do the work that my non-default constructor does, so that the WS client can access those instead of the constructor. K.O.