0

I've a WSDL XSD with request & response complex type elements defined.

  <xsd:complexType name="authPartyRequest">
       <xsd:sequence>
          <xsd:element name="Party" type="ICI-CAAS:Party" minOccurs="1" maxOccurs="1"/>
          <xsd:element name="Address" type="ICI-CAAS:Address" minOccurs="1" maxOccurs="1"/>
       </xsd:sequence>
  <xsd:complexType>


  <xsd:complexType name="authPartyResponse">
       <xsd:sequence>
          <xsd:element name="Channel" type="ICI-CAAS:Channel" minOccurs="1" maxOccurs="1"/>
          <xsd:element name="Event" type="ICI-CAAS:Event" minOccurs="0" maxOccurs="1"/>
          <xsd:element name="Party" type="ICI-CAAS:Party" minOccurs="0" maxOccurs="1"/>
       </xsd:sequence>
  <xsd:complexType>

and WSDL has portType definition including

   <wsdl:operation name="authenticateParty">
       <wsdl:input message="ICI-CAAS:authPartyRequst" />
       <wsdl:output message="ICI-CAAS:authPartyResponse" />  --> method response type
   </wsdl:operation>

When I generate the stubs using JAX-RPC (with WAS 6.1 run time) I'm seeing port type interface is generated with operation having response as 'void'. How ever I see request parameter is passed correctly.

  public interface AuthManagerService_PortType extends java.rmi.Remote
  {
   public void authenticateParty(AuthPartyRequest req); --> generating response type 'void'
  }

Can any one please help on priority?

ItsMyFist
  • 75
  • 7
  • Why don't you paste the full WSDL. – Scott Kurz Jun 13 '16 at 01:31
  • Unless you had a copy and paste error, I would have expected the opposite result, an operation with a return type but no input parameter because you have a typo in the declaration of your wsdl:input, "", request is misspelled. – F Rowe Jun 13 '16 at 13:30

0 Answers0