axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 26545] New: - WSDL2Java missing inout (Holder) argument
Date Fri, 30 Jan 2004 02:24:06 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26545>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26545

WSDL2Java missing inout (Holder) argument

           Summary: WSDL2Java missing inout (Holder) argument
           Product: Axis
           Version: current (nightly)
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: WSDL processing
        AssignedTo: axis-dev@ws.apache.org
        ReportedBy: ksmakoto@dd.iij4u.or.jp


WSDL2Java miss inout (Holder) argument, if it is WRAPPED-LITERAL style with one
input parameter and one output parameter.

I'll show samples (whole description are at files in attachment)

========

1 in - 1 out (fail pattern)

WSDL
--
<xsd:element name="hogeMethod">
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="inout0" type="xsd:int"/>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>

<xsd:element name="hogeMethodResponse">
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="inout0" type="xsd:int"/>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>

----

Java source code for PortType
--
public interface HogePortType extends java.rmi.Remote {
    public int hogeMethod(int hogeMethodInout0) throws java.rmi.RemoteException;
}

========

2 in - 1 out (success pattern)

WSDL
--
<xsd:element name="hogeMethod">
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="in0" type="xsd:int"/>
      <xsd:element name="inout0" type="xsd:int"/>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>

<xsd:element name="hogeMethodResponse">
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="inout0" type="xsd:int"/>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>

----

Java source code for PortType
--
public interface HogePortType extends java.rmi.Remote {
    public void hogeMethod(int hogeMethodIn0, javax.xml.rpc.holders.IntHolder
hogeMethodInout0) throws java.rmi.RemoteException;
}

========

2 in - 1 out (success pattern)

WSDL
--
<xsd:element name="hogeMethod">
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="inout0" type="xsd:int"/>
      <xsd:element name="in0" type="xsd:int"/>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>

<xsd:element name="hogeMethodResponse">
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="inout0" type="xsd:int"/>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>

----

Java source code for PortType
--
public interface HogePortType extends java.rmi.Remote {
    public void hogeMethod(javax.xml.rpc.holders.IntHolder hogeMethodInout0, int
hogeMethodIn0) throws java.rmi.RemoteException;
}

========

1 in - 2 out (success pattern)

WSDL
--
<xsd:element name="hogeMethod">
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="inout0" type="xsd:int"/>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>

<xsd:element name="hogeMethodResponse">
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="hogeMethodReturn" type="xsd:int"/>
      <xsd:element name="inout0" type="xsd:int"/>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>

----

Java source code for PortType
--
public interface HogePortType extends java.rmi.Remote {
    public int hogeMethod(javax.xml.rpc.holders.IntHolder hogeMethodInout0)
throws java.rmi.RemoteException;
}

========

Mime
View raw message