You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by "John Hawkins (JIRA)" <ax...@ws.apache.org> on 2005/09/22 11:15:30 UTC
[jira] Updated: (AXISCPP-832) WSDL2Ws does not create server side correctly for wsdls containing attachment types
[ http://issues.apache.org/jira/browse/AXISCPP-832?page=all ]
John Hawkins updated AXISCPP-832:
---------------------------------
Component: WSDL processing - Doc
Description:
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.
was:
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.
Version: 1.6 Alpha
> 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
>
> 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