Mailing-List: contact axis-c-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache AXIS C Developers List" <axis-c-dev@ws.apache.org>
Message-ID: <1444443575.1096614632314.JavaMail.apache@nagoya>
Date: Fri, 1 Oct 2004 00:10:32 -0700 (PDT)
From: axis-c-dev@ws.apache.org
To: axis-c-dev@ws.apache.org
Subject: [jira] Closed: (AXISCPP-159) WSDL2Ws fails to create stubs correctly
 for DOC Literal WSDL
In-Reply-To: <584865046.1095351577335.JavaMail.apache@nagoya>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Message:

   The following issue has been closed.

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/AXISCPP-159

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: AXISCPP-159
    Summary: WSDL2Ws fails to create stubs correctly for DOC Literal WSDL
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: FIXED

    Project: Axis-C++
 Components: 
             WSDL processing
   Versions:
             1.3 Beta

   Assignee: Nithyakala
   Reporter: Andrew Perry

    Created: Thu, 16 Sep 2004 9:18 AM
    Updated: Fri, 1 Oct 2004 12:10 AM
Environment: Linux

Description:
The Axis FV Tests wsdl for the RpcHttp... tests is an RPC wsdl. I created a DOC literal version of the wsdl and ran wsdl2ws but the stub header and cpp file generation was missing some data types.

----- code snippet from doc literal generated header ------
public:
    xsd__boolean echoBoolean(xsd__boolean Value0);
    xsd__decimal echoDecimal(xsd__decimal Value0);
     echoHexBinary( Value0);
    xsd__dateTime echoDate(xsd__dateTime Value0);
     echoBase64( Value0);
-------------------------

As can be seen the xsd__base64Binary and xsd__hexBinary data types are missing. This is the same in the generated.cpp file.

This works for the RCP wsdl.


---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira