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: <557391380.1127966748615.JavaMail.jira@ajax.apache.org>
Date: Thu, 29 Sep 2005 06:05:48 +0200 (CEST)
From: "Dushshantha Chandradasa (JIRA)" <axis-c-dev@ws.apache.org>
To: axis-c-dev@ws.apache.org
Subject: [jira] Commented: (AXISCPP-832) WSDL2Ws does not create server side
 correctly for wsdls containing attachment types
In-Reply-To: <1258042352.1127379989873.JavaMail.jira@ajax.apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/AXISCPP-832?page=comments#action_12330772 ] 

Dushshantha Chandradasa commented on AXISCPP-832:
-------------------------------------------------

i fixed this issue. But still there are problems in server side wrapper generation for attachments. i'll close this issue and create a seperate issue for that

> WSDL2Ws does not create server side correctly for wsdls containing attachment types
> -----------------------------------------------------------------------------------
>
>          Key: AXISCPP-832
>          URL: http://issues.apache.org/jira/browse/AXISCPP-832
>      Project: Axis-C++
>         Type: Bug
>   Components: WSDL processing - Doc
>     Versions: 1.6 Alpha
>     Reporter: James Jose
>     Assignee: Dushshantha Chandradasa

>
> When WSDL2Ws is used to create client side, attachment types like Image, PlainText, Source, octet-stream, and DataHandler are correctly  mapped to ISoapAttachment. But when server side is created these attachment types are not mapping to 'ISoapAttachment'.
> When WSDL2Ws tool is run against Attachment1.wsdl(available in the wsdl directory), in the client side it creates the following function prototype.
> xsd__int put(ISoapAttachment *Value0, ISoapAttachment *Value1, ISoapAttachment *Value2, ISoapAttachment *Value3, ISoapAttachment *Value4, ISoapAttachment *Value5, ISoapAttachment *Value6);
> ie all the attachment types are mapped to ISoapAttachment type.
> But when server side is created, function prototype looks like
> xsd__int put(Image Value0,PlainText Value1,Source Value2,octet-stream Value3,DataHandler Value4,DataHandler Value5,DataHandler Value6);
> ie WSDL2Ws uses the same type present in the WSDL as the data type.

-- 
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