[BEEHIVE-852] Service control generation incorrect for RPC Encoded style WSDLs

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: V1Beta, v1m1
• Component/s: System Controls
• Assignee: Nathan Jantz
• Reporter: Chad Schoettger
• Created: 21/Jul/05 05:23
• Updated: 26/Jul/06 22:23
• Resolved: 28/Jul/05 06:07

Description

Found while working on the service control DRT's:

If I generate a service control from a WSDL for an RPC encoded webservice, 'soapenc' types are always being replaced by java.lang.Object. For example:

Say my webservice method looks like:
public Boolean echoBoolean(Boolean inputBoolean)

And has the following WSDL representation:

(here's a fragment of my WSDL)
.
.
.
<wsdl:message name="echoBooleanResponse">
<wsdl:part name="return" type="soapenc:boolean"/>
</wsdl:message>
<wsdl:message name="echoBooleanRequest">
<wsdl:part name="inputBoolean" type="soapenc:boolean"/>
</wsdl:message>
<wsdl:operation name="echoBoolean" parameterOrder="inputBoolean">
<wsdl:input message="impl:echoBooleanRequest" name="echoBooleanRequest"/>
<wsdl:output message="impl:echoBooleanResponse" name="echoBooleanResponse"/>
</wsdl:operation>

The generated web service control method will look like:

public Object echoBoolean(Object inputBoolean);

The service control generator should not ignore the 'soapenc' types and instead use them to generate a more proper service control method, such as:

public Boolean echoBoolean(Boolean inputBoolean)

***********************************************************************

I have a patch for this which I will get posted in the next day or two.