WebLogic 10.3 clientgen missing .java for complexType

Question

Hi Everyone,
I am attempting to upgrade some WebLogic 8.1 code to 10.3. Part of this code base has a webservice call another webservice. In the 8.1 code base the original author used a Beehive control. Since that didn't work and it is retired I decided to use a more traditional approach using the <clientgen> ANT task. It all seems to work, but it looks like I have been shorted a few .java files. For example:
Foo_saved_wsdl.wsdl contains this snippet:
<s:element name="UpdateData">
<s:complexType>
<s:sequence>
<s:element maxOccurs="1" minOccurs="1" name="San" type="tns:SanName"/>
<s:element maxOccurs="1" minOccurs="1" name="objSanData" type="tns:SanData"/>
</s:sequence>
</s:complexType>
</s:element>
<s:simpleType name="SanName">
<s:restriction base="s:string">
<s:enumeration value="Foo1"/>
<s:enumeration value="Foo2"/>
</s:restriction>
</s:simpleType>
I was thus not surprised to see a SanName.java be generated. But...
<s:element name="THECreds" type="tns:THECreds"/>
<s:complexType name="THECreds">
<s:sequence>
<s:element maxOccurs="1" minOccurs="1" name="ConsName" type="tns:ConsName"/>
<s:element maxOccurs="1" minOccurs="0" name="ConsKey" type="s:string"/>
<s:element maxOccurs="1" minOccurs="0" name="MYAccount" type="s:string"/>
</s:sequence>
<s:anyAttribute/>
</s:complexType>
<s:simpleType name="ConsName">
<s:restriction base="s:string">
<s:enumeration value="Bar1"/>
<s:enumeration value="Bar2"/>
</s:restriction>
</s:simpleType>
no ConsName.java was generated. Is there something special one must do since THECreds is a complexType?
Regards,
-Randy

Answer 1

Hi Again,
My question did not supply a complete picture. In the 8.1 code base I can see the developer created a Java String object that contained a SOAP Header element like so...
<SOAP-ENV:Header
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<tns:THECreds xmlns:tns="http://tempuri.org/WXYZ/ABCServices">
<tns:ConsName xmlns:tns="http://tempuri.org/WXYZ/ABCServices">
ConsNameData
</tns:ConsName>
<tns:ConsKey xmlns:tns="http://tempuri.org/WXYZ/ABCServices">
ConsKeyData
</tns:ConsKey>
<tns:MYAccount xmlns:tns="http://tempuri.org/WXYZ/ABCServices">
AccountData
</tns:MYAccount>
</tns:THECreds>
</SOAP-ENV:Header>
When I call the webservice now I can see the XML going across the wire has an empty Header element. Thus even if I could get <clientgen> to create ConsName.java file I will still need the results to land in the SOAP Header element. Any comments on manipulating the Header element moi bien!
Regards,
-Randy