Service control generation incorrect for RPC Encoded style WSDLs
----------------------------------------------------------------

         Key: BEEHIVE-852
         URL: http://issues.apache.org/jira/browse/BEEHIVE-852
     Project: Beehive
        Type: Bug
  Components: System Controls  
    Versions: TBD    
    Reporter: Chad Schoettger


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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

Reply via email to