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 Amila Rathnayake <am...@opensource.lk> on 2004/08/03 13:40:10 UTC
RE: Supporting for Non-Wrapped WSDL's
Hi All,
Right now Axis C++ is supporting for wrapped style WSDL files.
Non-wrapped style WSDL 's are not supported and currently all the
doc-lit WSDL's are considered as wrapped style by default and generating
the Skeletons and Stubs accordingly by the WSDL2WS tool.
I have implemented the support for non-wrapped style wsdl. But for
testing purposes I need several valid WSDL's of non-wrapped style.
I've found a simple WSDL which is in non-wrapped style. But that WSDL is
having more than one part in the message. Then this should be an invalid
wsdl since in the doc-lit type we can have only one part in the message.
<wsdl:message name="loadXMLDataRequest">
<wsdl:part name="in0" element="impl:in0"/>
<wsdl:part name="in1" element="impl:in1"/>
</wsdl:message>
I have attached the relevant WSDL file here with.
If you have any idea, please comment on this.
Btw if you have come across any non-wrapped style wsdl file, please send
that file.
Thanks and Regards,
Amila Rathnayake.
> -----Original Message-----
> From: amilar@opensource.lk [mailto:amilar@opensource.lk]
> Sent: Wednesday, July 21, 2004 6:31 PM
> To: Apache AXIS C Developers List
> Subject: Supporting for Non-Wrapped WSDL's
>
> Hi All,
>
> At this moment Axis is assuming and supporting only for Wrapped style
> WSDL's.
>
> In wrapped style WSDL's, all method parameters are wrapped inside an
> element named as the same name as operation and of the type of
> xsd:complextype.
>
> Ex: Wrapped Style
> -----------------
>
> ...
> <types>
> <xsd:schema targetNamespace="http://www.sample.org/" >
> <xsd:element name="countWords">
> <xsd:complexType>
> <xsd:sequence>
> <xsd:element name="words" type="xsd:string" />
> </xsd:sequence>
> </xsd:complexType>
> </xsd:element>
> </xsd:schema>
> </types>
> <message name="countWordsInput">
> <part name="iInputText" element="tns:countWords" />
> </message>
> ...
>
> non-wrapped style
> =================
> But in Non-Wrapped style type is declared in the element tag.
> If you have overloaded operations, you cannot use the document/literal
> wrapped style.
> WSDL allows overloaded operations. But when you add the wrapped
pattern to
> WSDL you require an element to have the same name as the operation,
and
> you cannot have two elements with the same name in XML. So you must
use
> the document/literal, non-wrapped style or one of the RPC styles
>
> Eg: non-wrapped style
> ----------------------
>
> ...
> <types>
> <xsd:schema targetNamespace="http://www.sample.org/" >
> <xsd:element name="countWords" type="xsd:string" />
> </xsd:schema>
> </types>
> <message name="countWordsInput">
> <part name="iInputText" element="tns:countWords" />
> </message>
> ...
>
> Currently I am working on this and implementing the support for
> non-wrapped style wsdl's.
>
> Regards,
> Amila Rathnayake.
>
>
RE: Supporting for Non-Wrapped WSDL's
Posted by Amila Rathnayake <am...@opensource.lk>.
Hi Damitha,
Here are some links to refer and you can have some rough idea on this.
http://www-106.ibm.com/developerworks/webservices/library/ws-whichwsdl/
http://www-106.ibm.com/developerworks/webservices/library/ws-whichwsdl/#
resources
Regards,
Amila.
> -----Original Message-----
> From: damitha kumarage [mailto:damitha@opensource.lk]
> Sent: Wednesday, August 04, 2004 2:25 PM
> To: Apache AXIS C Developers List
> Subject: RE: Supporting for Non-Wrapped WSDL's
>
> Hi Amila,
>
> I'm confused about this overloaded and nonwrapped stuff. Could someone
> point me towards more reading on this stuff
>
> thanks
> damitha
> On Tue, 2004-08-03 at 17:40, Amila Rathnayake wrote:
> > Hi All,
> >
> > Right now Axis C++ is supporting for wrapped style WSDL files.
> > Non-wrapped style WSDL 's are not supported and currently all the
> > doc-lit WSDL's are considered as wrapped style by default and
generating
> > the Skeletons and Stubs accordingly by the WSDL2WS tool.
> >
> > I have implemented the support for non-wrapped style wsdl. But for
> > testing purposes I need several valid WSDL's of non-wrapped style.
> >
> > I've found a simple WSDL which is in non-wrapped style. But that
WSDL is
> > having more than one part in the message. Then this should be an
invalid
> > wsdl since in the doc-lit type we can have only one part in the
message.
> >
> > <wsdl:message name="loadXMLDataRequest">
> >
> > <wsdl:part name="in0" element="impl:in0"/>
> >
> > <wsdl:part name="in1" element="impl:in1"/>
> >
> > </wsdl:message>
> >
> > I have attached the relevant WSDL file here with.
> >
> > If you have any idea, please comment on this.
> >
> > Btw if you have come across any non-wrapped style wsdl file, please
send
> > that file.
> >
> > Thanks and Regards,
> > Amila Rathnayake.
> >
> >
> >
> >
> > > -----Original Message-----
> > > From: amilar@opensource.lk [mailto:amilar@opensource.lk]
> > > Sent: Wednesday, July 21, 2004 6:31 PM
> > > To: Apache AXIS C Developers List
> > > Subject: Supporting for Non-Wrapped WSDL's
> > >
> > > Hi All,
> > >
> > > At this moment Axis is assuming and supporting only for Wrapped
style
> > > WSDL's.
> > >
> > > In wrapped style WSDL's, all method parameters are wrapped inside
an
> > > element named as the same name as operation and of the type of
> > > xsd:complextype.
> > >
> > > Ex: Wrapped Style
> > > -----------------
> > >
> > > ...
> > > <types>
> > > <xsd:schema targetNamespace="http://www.sample.org/" >
> > > <xsd:element name="countWords">
> > > <xsd:complexType>
> > > <xsd:sequence>
> > > <xsd:element name="words" type="xsd:string" />
> > > </xsd:sequence>
> > > </xsd:complexType>
> > > </xsd:element>
> > > </xsd:schema>
> > > </types>
> > > <message name="countWordsInput">
> > > <part name="iInputText" element="tns:countWords" />
> > > </message>
> > > ...
> > >
> > > non-wrapped style
> > > =================
> > > But in Non-Wrapped style type is declared in the element tag.
> > > If you have overloaded operations, you cannot use the
document/literal
> > > wrapped style.
> > > WSDL allows overloaded operations. But when you add the wrapped
> > pattern to
> > > WSDL you require an element to have the same name as the
operation,
> > and
> > > you cannot have two elements with the same name in XML. So you
must
> > use
> > > the document/literal, non-wrapped style or one of the RPC styles
> > >
> > > Eg: non-wrapped style
> > > ----------------------
> > >
> > > ...
> > > <types>
> > > <xsd:schema targetNamespace="http://www.sample.org/" >
> > > <xsd:element name="countWords" type="xsd:string" />
> > > </xsd:schema>
> > > </types>
> > > <message name="countWordsInput">
> > > <part name="iInputText" element="tns:countWords" />
> > > </message>
> > > ...
> > >
> > > Currently I am working on this and implementing the support for
> > > non-wrapped style wsdl's.
> > >
> > > Regards,
> > > Amila Rathnayake.
> > >
> > >
> >
>
RE: Supporting for Non-Wrapped WSDL's
Posted by damitha kumarage <da...@opensource.lk>.
Hi Amila,
I'm confused about this overloaded and nonwrapped stuff. Could someone
point me towards more reading on this stuff
thanks
damitha
On Tue, 2004-08-03 at 17:40, Amila Rathnayake wrote:
> Hi All,
>
> Right now Axis C++ is supporting for wrapped style WSDL files.
> Non-wrapped style WSDL 's are not supported and currently all the
> doc-lit WSDL's are considered as wrapped style by default and generating
> the Skeletons and Stubs accordingly by the WSDL2WS tool.
>
> I have implemented the support for non-wrapped style wsdl. But for
> testing purposes I need several valid WSDL's of non-wrapped style.
>
> I've found a simple WSDL which is in non-wrapped style. But that WSDL is
> having more than one part in the message. Then this should be an invalid
> wsdl since in the doc-lit type we can have only one part in the message.
>
> <wsdl:message name="loadXMLDataRequest">
>
> <wsdl:part name="in0" element="impl:in0"/>
>
> <wsdl:part name="in1" element="impl:in1"/>
>
> </wsdl:message>
>
> I have attached the relevant WSDL file here with.
>
> If you have any idea, please comment on this.
>
> Btw if you have come across any non-wrapped style wsdl file, please send
> that file.
>
> Thanks and Regards,
> Amila Rathnayake.
>
>
>
>
> > -----Original Message-----
> > From: amilar@opensource.lk [mailto:amilar@opensource.lk]
> > Sent: Wednesday, July 21, 2004 6:31 PM
> > To: Apache AXIS C Developers List
> > Subject: Supporting for Non-Wrapped WSDL's
> >
> > Hi All,
> >
> > At this moment Axis is assuming and supporting only for Wrapped style
> > WSDL's.
> >
> > In wrapped style WSDL's, all method parameters are wrapped inside an
> > element named as the same name as operation and of the type of
> > xsd:complextype.
> >
> > Ex: Wrapped Style
> > -----------------
> >
> > ...
> > <types>
> > <xsd:schema targetNamespace="http://www.sample.org/" >
> > <xsd:element name="countWords">
> > <xsd:complexType>
> > <xsd:sequence>
> > <xsd:element name="words" type="xsd:string" />
> > </xsd:sequence>
> > </xsd:complexType>
> > </xsd:element>
> > </xsd:schema>
> > </types>
> > <message name="countWordsInput">
> > <part name="iInputText" element="tns:countWords" />
> > </message>
> > ...
> >
> > non-wrapped style
> > =================
> > But in Non-Wrapped style type is declared in the element tag.
> > If you have overloaded operations, you cannot use the document/literal
> > wrapped style.
> > WSDL allows overloaded operations. But when you add the wrapped
> pattern to
> > WSDL you require an element to have the same name as the operation,
> and
> > you cannot have two elements with the same name in XML. So you must
> use
> > the document/literal, non-wrapped style or one of the RPC styles
> >
> > Eg: non-wrapped style
> > ----------------------
> >
> > ...
> > <types>
> > <xsd:schema targetNamespace="http://www.sample.org/" >
> > <xsd:element name="countWords" type="xsd:string" />
> > </xsd:schema>
> > </types>
> > <message name="countWordsInput">
> > <part name="iInputText" element="tns:countWords" />
> > </message>
> > ...
> >
> > Currently I am working on this and implementing the support for
> > non-wrapped style wsdl's.
> >
> > Regards,
> > Amila Rathnayake.
> >
> >
>
RE: Supporting for Non-Wrapped WSDL's
Posted by Samisa Abeysinghe <sa...@yahoo.com>.
Any luck with the list of links that I sent earlier?
Samisa...
--- Amila Rathnayake <am...@opensource.lk> wrote:
>
>
> Hi,
>
> If any of you have come across a simple non-wrapped style wsdl please
> send it to me for further testing.
>
> Thanks and Regards,
> Amila Rathnayake.
>
>
>
> > -----Original Message-----
> > From: Amila Rathnayake [mailto:amilar@opensource.lk]
> > Sent: Thursday, August 05, 2004 7:20 PM
> > To: 'Apache AXIS C Developers List'
> > Subject: RE: Supporting for Non-Wrapped WSDL's
> >
> >
> >
> > Hi All,
> >
> > I have amended the GatewayWebService.wsdl that I've sent you early and
> > make it a valid non-wrapped wsdl. The earlier one had 2 parts in a
> > message body.
> >
> > Here I am sending the new wsdl and can somebody check this and say
> > whether this is a valid wsdl.
> >
> > I have generated the server side and client side by using the latest
> > axis jars and with -wnonwrapped command line option. The generated
> code
> > seems to be ok. I compiled the server and client as well and it
> compiled
> > without any errors.
> >
> > Thanks and Regards,
> > Amila Rathnayake.
> >
> >
> >
> >
> > > -----Original Message-----
> > > From: Amila Rathnayake [mailto:amilar@opensource.lk]
> > > Sent: Wednesday, August 04, 2004 6:33 PM
> > > To: 'Apache AXIS C Developers List'
> > > Cc: sanjiva@opensource.lk
> > > Subject: RE: Supporting for Non-Wrapped WSDL's
> > >
> > >
> > >
> > > Hi All,
> > >
> > > I still have two problems to clarify with my implementation of
> > > non-wrapped style wsdl support.
> > >
> > >
> > > 1).
> > >
> > > Theoretically in wrapped style wsdl's we can have same name for
> > > operation name and parameter name for that operation. But if we have
> > the
> > > same name for operation and parameter in non-wrapped wsdl, is it a
> > > valid/correct wsdl?
> > >
> > > Please clarify me if anybody has an idea on this.
> > >
> > >
> > > 2).
> > >
> > > In the stub header at the client side, it adds the code for include
> > > header files for arrays defined in the complex types. But actually
> > that
> > > array represents a simple type and therefore it will not generate
> > > separate class for that type. Then it will give errors at the
> > > compilation since it can't find the particular header file.
> > >
> > > For example ;
> > >
> > > <s:complexType name="Thing" final="restriction">
> > > <s:sequence>
> > > <s:element ref="s0:aThing" minOccurs="0" maxOccurs="unbounded"/>
> > > <s:element ref="s0:otherData" minOccurs="0"
> > maxOccurs="unbounded"/>
> > > </s:sequence>
> > > </s:complexType>
> > >
> > > But actually aThing is a simple type
> > >
> > > <s:simpleType name="aThing">
> > > <s:restriction base="s:string">
> > > <s:maxLength value="255"/>
> > > </s:restriction>
> > > </s:simpleType>
> > >
> > > I have to work on this and have to stop the adding of lines to
> include
> > > the header files for arrays in complex types and those arrays are
> > > actually simple types and that is defined in other place of the
> wsdl.
> > >
> > > Thanks and regards,
> > > Amila.
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: Amila Rathnayake [mailto:amilar@opensource.lk]
> > > > Sent: Wednesday, August 04, 2004 3:39 PM
> > > > To: 'Apache AXIS C Developers List'
> > > > Subject: RE: Supporting for Non-Wrapped WSDL's
> > > >
> > > >
> > > >
> > > > Hi All,
> > > >
> > > > I regret to say that still nobody has commented on my issue and I
> > > really
> > > > want your comments on this to make sure that the generated code
> for
> > > > non-wrapped style is correct. I have generated both the server
> side
> > > and
> > > > client side. I also checked the differences in generated codes for
> > > > server and client sides in both wrapped and non-wrapped styles and
> > it
> > > > looks correct for me. But still your comments on this are really
> > > > appreciated.
> > > >
> > > > I am sending the relevant diff file for the changes I've made on
> > > > WSDL2Ws.java and you can apply this patch and test for non-wrapped
> > > style
> > > > wsdl's.
> > > >
> > > > With this change you can give a command line argument to generate
> in
> > > > non-wrapped style. If you don't give any command line argument for
> > the
> > > > wsdl2ws tool it will generate for wrapped style by default.
> > > >
> > > > For example for client side ;
> > > >
> > > > Java -classpath ./wsdl2ws.jar;%classpath%
> > > > org.apache.axis.wsdl.wsdl2ws.WSDL2Ws <*.wsdl> -o./ClientOut -lc++
> > > > -sclient -wnonwrapped
> > > >
> > > > -w wrapping style of the WSDL (wrapped|nonwrapped) - default is
> > > wrapped
> > > >
> > > > Please try this out and send your comments.
> > > >
> > > > Thanks and Regards,
> > > > Amila Rathnayake.
> > > >
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: Amila Rathnayake [mailto:amilar@opensource.lk]
> > > > > Sent: Tuesday, August 03, 2004 6:37 PM
> > > > > To: 'Apache AXIS C Developers List'
> > > > > Subject: RE: Supporting for Non-Wrapped WSDL's
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > Hi All,
> > > > >
> > > > > Theoretically it should be able to generate valid skeletons and
> > > stubs
> > > > in
> > > > > the non-wrapped style by even using a wrapped style wsdl's.
> > > > >
> > > > > So that I have used a wrapped style wsdl and generated server
> > > > skeletons
> > > > > in the non-wrapped style.
> > > > >
> > > > > I have added the relevant wrapped style wsdl here with and
> > following
> > > > are
> > > > > the differences between wrapped style code generation and
> > > non-wrapped
> > > > > style code generation by using the same wsdl file.
> > > > >
> > > > > Here I have given only the places where the generated code is
> > > > different
> > > > > in two styles. Except the following all the other files and
> codes
> > > > > generated by the wsdl2ws tool are same.
> > > > >
> > > > > By looking at the following codes you can find the differences
> > > between
> > > > > the code generation in two styles.
> > > > >
> > > > > thing.h and thing.cpp
> > > > > ======================
> > > > > in wrapped style
> > > > > ------------------
> > > > > void find_aThing(aThing Value0, AXIS_OUT_PARAM aThing_Array*
> > > > OutValue0,
> > > > > AXIS_OUT_PARAM otherData_Array* OutValue1);
> > > > >
>
=== message truncated ===
__________________________________
Do you Yahoo!?
Y! Messenger - Communicate in real time. Download now.
http://messenger.yahoo.com
RE: Supporting for Non-Wrapped WSDL's
Posted by Samisa Abeysinghe <sa...@yahoo.com>.
Any luck with the list of links that I sent earlier?
Samisa...
--- Amila Rathnayake <am...@opensource.lk> wrote:
>
>
> Hi,
>
> If any of you have come across a simple non-wrapped style wsdl please
> send it to me for further testing.
>
> Thanks and Regards,
> Amila Rathnayake.
>
>
>
> > -----Original Message-----
> > From: Amila Rathnayake [mailto:amilar@opensource.lk]
> > Sent: Thursday, August 05, 2004 7:20 PM
> > To: 'Apache AXIS C Developers List'
> > Subject: RE: Supporting for Non-Wrapped WSDL's
> >
> >
> >
> > Hi All,
> >
> > I have amended the GatewayWebService.wsdl that I've sent you early and
> > make it a valid non-wrapped wsdl. The earlier one had 2 parts in a
> > message body.
> >
> > Here I am sending the new wsdl and can somebody check this and say
> > whether this is a valid wsdl.
> >
> > I have generated the server side and client side by using the latest
> > axis jars and with -wnonwrapped command line option. The generated
> code
> > seems to be ok. I compiled the server and client as well and it
> compiled
> > without any errors.
> >
> > Thanks and Regards,
> > Amila Rathnayake.
> >
> >
> >
> >
> > > -----Original Message-----
> > > From: Amila Rathnayake [mailto:amilar@opensource.lk]
> > > Sent: Wednesday, August 04, 2004 6:33 PM
> > > To: 'Apache AXIS C Developers List'
> > > Cc: sanjiva@opensource.lk
> > > Subject: RE: Supporting for Non-Wrapped WSDL's
> > >
> > >
> > >
> > > Hi All,
> > >
> > > I still have two problems to clarify with my implementation of
> > > non-wrapped style wsdl support.
> > >
> > >
> > > 1).
> > >
> > > Theoretically in wrapped style wsdl's we can have same name for
> > > operation name and parameter name for that operation. But if we have
> > the
> > > same name for operation and parameter in non-wrapped wsdl, is it a
> > > valid/correct wsdl?
> > >
> > > Please clarify me if anybody has an idea on this.
> > >
> > >
> > > 2).
> > >
> > > In the stub header at the client side, it adds the code for include
> > > header files for arrays defined in the complex types. But actually
> > that
> > > array represents a simple type and therefore it will not generate
> > > separate class for that type. Then it will give errors at the
> > > compilation since it can't find the particular header file.
> > >
> > > For example ;
> > >
> > > <s:complexType name="Thing" final="restriction">
> > > <s:sequence>
> > > <s:element ref="s0:aThing" minOccurs="0" maxOccurs="unbounded"/>
> > > <s:element ref="s0:otherData" minOccurs="0"
> > maxOccurs="unbounded"/>
> > > </s:sequence>
> > > </s:complexType>
> > >
> > > But actually aThing is a simple type
> > >
> > > <s:simpleType name="aThing">
> > > <s:restriction base="s:string">
> > > <s:maxLength value="255"/>
> > > </s:restriction>
> > > </s:simpleType>
> > >
> > > I have to work on this and have to stop the adding of lines to
> include
> > > the header files for arrays in complex types and those arrays are
> > > actually simple types and that is defined in other place of the
> wsdl.
> > >
> > > Thanks and regards,
> > > Amila.
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: Amila Rathnayake [mailto:amilar@opensource.lk]
> > > > Sent: Wednesday, August 04, 2004 3:39 PM
> > > > To: 'Apache AXIS C Developers List'
> > > > Subject: RE: Supporting for Non-Wrapped WSDL's
> > > >
> > > >
> > > >
> > > > Hi All,
> > > >
> > > > I regret to say that still nobody has commented on my issue and I
> > > really
> > > > want your comments on this to make sure that the generated code
> for
> > > > non-wrapped style is correct. I have generated both the server
> side
> > > and
> > > > client side. I also checked the differences in generated codes for
> > > > server and client sides in both wrapped and non-wrapped styles and
> > it
> > > > looks correct for me. But still your comments on this are really
> > > > appreciated.
> > > >
> > > > I am sending the relevant diff file for the changes I've made on
> > > > WSDL2Ws.java and you can apply this patch and test for non-wrapped
> > > style
> > > > wsdl's.
> > > >
> > > > With this change you can give a command line argument to generate
> in
> > > > non-wrapped style. If you don't give any command line argument for
> > the
> > > > wsdl2ws tool it will generate for wrapped style by default.
> > > >
> > > > For example for client side ;
> > > >
> > > > Java -classpath ./wsdl2ws.jar;%classpath%
> > > > org.apache.axis.wsdl.wsdl2ws.WSDL2Ws <*.wsdl> -o./ClientOut -lc++
> > > > -sclient -wnonwrapped
> > > >
> > > > -w wrapping style of the WSDL (wrapped|nonwrapped) - default is
> > > wrapped
> > > >
> > > > Please try this out and send your comments.
> > > >
> > > > Thanks and Regards,
> > > > Amila Rathnayake.
> > > >
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: Amila Rathnayake [mailto:amilar@opensource.lk]
> > > > > Sent: Tuesday, August 03, 2004 6:37 PM
> > > > > To: 'Apache AXIS C Developers List'
> > > > > Subject: RE: Supporting for Non-Wrapped WSDL's
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > Hi All,
> > > > >
> > > > > Theoretically it should be able to generate valid skeletons and
> > > stubs
> > > > in
> > > > > the non-wrapped style by even using a wrapped style wsdl's.
> > > > >
> > > > > So that I have used a wrapped style wsdl and generated server
> > > > skeletons
> > > > > in the non-wrapped style.
> > > > >
> > > > > I have added the relevant wrapped style wsdl here with and
> > following
> > > > are
> > > > > the differences between wrapped style code generation and
> > > non-wrapped
> > > > > style code generation by using the same wsdl file.
> > > > >
> > > > > Here I have given only the places where the generated code is
> > > > different
> > > > > in two styles. Except the following all the other files and
> codes
> > > > > generated by the wsdl2ws tool are same.
> > > > >
> > > > > By looking at the following codes you can find the differences
> > > between
> > > > > the code generation in two styles.
> > > > >
> > > > > thing.h and thing.cpp
> > > > > ======================
> > > > > in wrapped style
> > > > > ------------------
> > > > > void find_aThing(aThing Value0, AXIS_OUT_PARAM aThing_Array*
> > > > OutValue0,
> > > > > AXIS_OUT_PARAM otherData_Array* OutValue1);
> > > > >
>
=== message truncated ===
__________________________________
Do you Yahoo!?
Y! Messenger - Communicate in real time. Download now.
http://messenger.yahoo.com
RE: Supporting for Non-Wrapped WSDL's
Posted by Amila Rathnayake <am...@opensource.lk>.
Hi,
If any of you have come across a simple non-wrapped style wsdl please
send it to me for further testing.
Thanks and Regards,
Amila Rathnayake.
> -----Original Message-----
> From: Amila Rathnayake [mailto:amilar@opensource.lk]
> Sent: Thursday, August 05, 2004 7:20 PM
> To: 'Apache AXIS C Developers List'
> Subject: RE: Supporting for Non-Wrapped WSDL's
>
>
>
> Hi All,
>
> I have amended the GatewayWebService.wsdl that I've sent you early and
> make it a valid non-wrapped wsdl. The earlier one had 2 parts in a
> message body.
>
> Here I am sending the new wsdl and can somebody check this and say
> whether this is a valid wsdl.
>
> I have generated the server side and client side by using the latest
> axis jars and with -wnonwrapped command line option. The generated
code
> seems to be ok. I compiled the server and client as well and it
compiled
> without any errors.
>
> Thanks and Regards,
> Amila Rathnayake.
>
>
>
>
> > -----Original Message-----
> > From: Amila Rathnayake [mailto:amilar@opensource.lk]
> > Sent: Wednesday, August 04, 2004 6:33 PM
> > To: 'Apache AXIS C Developers List'
> > Cc: sanjiva@opensource.lk
> > Subject: RE: Supporting for Non-Wrapped WSDL's
> >
> >
> >
> > Hi All,
> >
> > I still have two problems to clarify with my implementation of
> > non-wrapped style wsdl support.
> >
> >
> > 1).
> >
> > Theoretically in wrapped style wsdl's we can have same name for
> > operation name and parameter name for that operation. But if we have
> the
> > same name for operation and parameter in non-wrapped wsdl, is it a
> > valid/correct wsdl?
> >
> > Please clarify me if anybody has an idea on this.
> >
> >
> > 2).
> >
> > In the stub header at the client side, it adds the code for include
> > header files for arrays defined in the complex types. But actually
> that
> > array represents a simple type and therefore it will not generate
> > separate class for that type. Then it will give errors at the
> > compilation since it can't find the particular header file.
> >
> > For example ;
> >
> > <s:complexType name="Thing" final="restriction">
> > <s:sequence>
> > <s:element ref="s0:aThing" minOccurs="0" maxOccurs="unbounded"/>
> > <s:element ref="s0:otherData" minOccurs="0"
> maxOccurs="unbounded"/>
> > </s:sequence>
> > </s:complexType>
> >
> > But actually aThing is a simple type
> >
> > <s:simpleType name="aThing">
> > <s:restriction base="s:string">
> > <s:maxLength value="255"/>
> > </s:restriction>
> > </s:simpleType>
> >
> > I have to work on this and have to stop the adding of lines to
include
> > the header files for arrays in complex types and those arrays are
> > actually simple types and that is defined in other place of the
wsdl.
> >
> > Thanks and regards,
> > Amila.
> >
> >
> >
> > > -----Original Message-----
> > > From: Amila Rathnayake [mailto:amilar@opensource.lk]
> > > Sent: Wednesday, August 04, 2004 3:39 PM
> > > To: 'Apache AXIS C Developers List'
> > > Subject: RE: Supporting for Non-Wrapped WSDL's
> > >
> > >
> > >
> > > Hi All,
> > >
> > > I regret to say that still nobody has commented on my issue and I
> > really
> > > want your comments on this to make sure that the generated code
for
> > > non-wrapped style is correct. I have generated both the server
side
> > and
> > > client side. I also checked the differences in generated codes for
> > > server and client sides in both wrapped and non-wrapped styles and
> it
> > > looks correct for me. But still your comments on this are really
> > > appreciated.
> > >
> > > I am sending the relevant diff file for the changes I've made on
> > > WSDL2Ws.java and you can apply this patch and test for non-wrapped
> > style
> > > wsdl's.
> > >
> > > With this change you can give a command line argument to generate
in
> > > non-wrapped style. If you don't give any command line argument for
> the
> > > wsdl2ws tool it will generate for wrapped style by default.
> > >
> > > For example for client side ;
> > >
> > > Java -classpath ./wsdl2ws.jar;%classpath%
> > > org.apache.axis.wsdl.wsdl2ws.WSDL2Ws <*.wsdl> -o./ClientOut -lc++
> > > -sclient -wnonwrapped
> > >
> > > -w wrapping style of the WSDL (wrapped|nonwrapped) - default is
> > wrapped
> > >
> > > Please try this out and send your comments.
> > >
> > > Thanks and Regards,
> > > Amila Rathnayake.
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: Amila Rathnayake [mailto:amilar@opensource.lk]
> > > > Sent: Tuesday, August 03, 2004 6:37 PM
> > > > To: 'Apache AXIS C Developers List'
> > > > Subject: RE: Supporting for Non-Wrapped WSDL's
> > > >
> > > >
> > > >
> > > >
> > > > Hi All,
> > > >
> > > > Theoretically it should be able to generate valid skeletons and
> > stubs
> > > in
> > > > the non-wrapped style by even using a wrapped style wsdl's.
> > > >
> > > > So that I have used a wrapped style wsdl and generated server
> > > skeletons
> > > > in the non-wrapped style.
> > > >
> > > > I have added the relevant wrapped style wsdl here with and
> following
> > > are
> > > > the differences between wrapped style code generation and
> > non-wrapped
> > > > style code generation by using the same wsdl file.
> > > >
> > > > Here I have given only the places where the generated code is
> > > different
> > > > in two styles. Except the following all the other files and
codes
> > > > generated by the wsdl2ws tool are same.
> > > >
> > > > By looking at the following codes you can find the differences
> > between
> > > > the code generation in two styles.
> > > >
> > > > thing.h and thing.cpp
> > > > ======================
> > > > in wrapped style
> > > > ------------------
> > > > void find_aThing(aThing Value0, AXIS_OUT_PARAM aThing_Array*
> > > OutValue0,
> > > > AXIS_OUT_PARAM otherData_Array* OutValue1);
> > > >
> > > > in the non-wrapped style
> > > > --------------------------
> > > > void find_aThing(find_aThing* Value0, AXIS_OUT_PARAM
aThing_Array*
> > > > OutValue0, AXIS_OUT_PARAM otherData_Array* OutValue1);
> > > >
> > > >
> > > > thingwrapper.cpp
> > > > ================
> > > > in wrapped style
> > > > ------------------
> > > > xsd__string v0 = pIWSDZ->getElementAsString("aThing",0);
> > > >
> > > > in the non-wrapped style
> > > > --------------------------
> > > > find_aThing *v0 =
> > > >
> > >
> >
>
(find_aThing*)pIWSDZ->getCmplxObject((void*)Axis_DeSerialize_find_aThing
> > > > , (void*)Axis_Create_find_aThing,
> > > > (void*)Axis_Delete_find_aThing
> > > > , "find_aThing", Axis_URI_find_aThing);
> > > >
> > > >
> > > > Please have a look at those differences with the attached wsdl
and
> > > > comment on this.
> > > >
> > > > Thanks and Regards,
> > > > Amila Rathnayake.
> > > >
> > > >
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: Amila Rathnayake [mailto:amilar@opensource.lk]
> > > > > Sent: Tuesday, August 03, 2004 5:40 PM
> > > > > To: 'Apache AXIS C Developers List'; axis-c-user@ws.apache.org
> > > > > Subject: RE: Supporting for Non-Wrapped WSDL's
> > > > >
> > > > > Hi All,
> > > > >
> > > > > Right now Axis C++ is supporting for wrapped style WSDL files.
> > > > > Non-wrapped style WSDL 's are not supported and currently all
> the
> > > > > doc-lit WSDL's are considered as wrapped style by default and
> > > > generating
> > > > > the Skeletons and Stubs accordingly by the WSDL2WS tool.
> > > > >
> > > > > I have implemented the support for non-wrapped style wsdl. But
> for
> > > > > testing purposes I need several valid WSDL's of non-wrapped
> style.
> > > > >
> > > > > I've found a simple WSDL which is in non-wrapped style. But
that
> > > WSDL
> > > > is
> > > > > having more than one part in the message. Then this should be
an
> > > > invalid
> > > > > wsdl since in the doc-lit type we can have only one part in
the
> > > > message.
> > > > >
> > > > > <wsdl:message name="loadXMLDataRequest">
> > > > >
> > > > > <wsdl:part name="in0" element="impl:in0"/>
> > > > >
> > > > > <wsdl:part name="in1" element="impl:in1"/>
> > > > >
> > > > > </wsdl:message>
> > > > >
> > > > > I have attached the relevant WSDL file here with.
> > > > >
> > > > > If you have any idea, please comment on this.
> > > > >
> > > > > Btw if you have come across any non-wrapped style wsdl file,
> > please
> > > > send
> > > > > that file.
> > > > >
> > > > > Thanks and Regards,
> > > > > Amila Rathnayake.
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: amilar@opensource.lk [mailto:amilar@opensource.lk]
> > > > > > Sent: Wednesday, July 21, 2004 6:31 PM
> > > > > > To: Apache AXIS C Developers List
> > > > > > Subject: Supporting for Non-Wrapped WSDL's
> > > > > >
> > > > > > Hi All,
> > > > > >
> > > > > > At this moment Axis is assuming and supporting only for
> Wrapped
> > > > style
> > > > > > WSDL's.
> > > > > >
> > > > > > In wrapped style WSDL's, all method parameters are wrapped
> > inside
> > > an
> > > > > > element named as the same name as operation and of the type
of
> > > > > > xsd:complextype.
> > > > > >
> > > > > > Ex: Wrapped Style
> > > > > > -----------------
> > > > > >
> > > > > > ...
> > > > > > <types>
> > > > > > <xsd:schema targetNamespace="http://www.sample.org/" >
> > > > > > <xsd:element name="countWords">
> > > > > > <xsd:complexType>
> > > > > > <xsd:sequence>
> > > > > > <xsd:element name="words"
> type="xsd:string"
> > />
> > > > > > </xsd:sequence>
> > > > > > </xsd:complexType>
> > > > > > </xsd:element>
> > > > > > </xsd:schema>
> > > > > > </types>
> > > > > > <message name="countWordsInput">
> > > > > > <part name="iInputText" element="tns:countWords" />
> > > > > > </message>
> > > > > > ...
> > > > > >
> > > > > > non-wrapped style
> > > > > > =================
> > > > > > But in Non-Wrapped style type is declared in the element
tag.
> > > > > > If you have overloaded operations, you cannot use the
> > > > document/literal
> > > > > > wrapped style.
> > > > > > WSDL allows overloaded operations. But when you add the
> wrapped
> > > > > pattern to
> > > > > > WSDL you require an element to have the same name as the
> > > operation,
> > > > > and
> > > > > > you cannot have two elements with the same name in XML. So
you
> > > must
> > > > > use
> > > > > > the document/literal, non-wrapped style or one of the RPC
> styles
> > > > > >
> > > > > > Eg: non-wrapped style
> > > > > > ----------------------
> > > > > >
> > > > > > ...
> > > > > > <types>
> > > > > > <xsd:schema targetNamespace="http://www.sample.org/" >
> > > > > > <xsd:element name="countWords" type="xsd:string" />
> > > > > > </xsd:schema>
> > > > > > </types>
> > > > > > <message name="countWordsInput">
> > > > > > <part name="iInputText" element="tns:countWords" />
> > > > > > </message>
> > > > > > ...
> > > > > >
> > > > > > Currently I am working on this and implementing the support
> for
> > > > > > non-wrapped style wsdl's.
> > > > > >
> > > > > > Regards,
> > > > > > Amila Rathnayake.
> > > > > >
> > > > > >
> >
RE: Supporting for Non-Wrapped WSDL's
Posted by Amila Rathnayake <am...@opensource.lk>.
Hi,
If any of you have come across a simple non-wrapped style wsdl please
send it to me for further testing.
Thanks and Regards,
Amila Rathnayake.
> -----Original Message-----
> From: Amila Rathnayake [mailto:amilar@opensource.lk]
> Sent: Thursday, August 05, 2004 7:20 PM
> To: 'Apache AXIS C Developers List'
> Subject: RE: Supporting for Non-Wrapped WSDL's
>
>
>
> Hi All,
>
> I have amended the GatewayWebService.wsdl that I've sent you early and
> make it a valid non-wrapped wsdl. The earlier one had 2 parts in a
> message body.
>
> Here I am sending the new wsdl and can somebody check this and say
> whether this is a valid wsdl.
>
> I have generated the server side and client side by using the latest
> axis jars and with -wnonwrapped command line option. The generated
code
> seems to be ok. I compiled the server and client as well and it
compiled
> without any errors.
>
> Thanks and Regards,
> Amila Rathnayake.
>
>
>
>
> > -----Original Message-----
> > From: Amila Rathnayake [mailto:amilar@opensource.lk]
> > Sent: Wednesday, August 04, 2004 6:33 PM
> > To: 'Apache AXIS C Developers List'
> > Cc: sanjiva@opensource.lk
> > Subject: RE: Supporting for Non-Wrapped WSDL's
> >
> >
> >
> > Hi All,
> >
> > I still have two problems to clarify with my implementation of
> > non-wrapped style wsdl support.
> >
> >
> > 1).
> >
> > Theoretically in wrapped style wsdl's we can have same name for
> > operation name and parameter name for that operation. But if we have
> the
> > same name for operation and parameter in non-wrapped wsdl, is it a
> > valid/correct wsdl?
> >
> > Please clarify me if anybody has an idea on this.
> >
> >
> > 2).
> >
> > In the stub header at the client side, it adds the code for include
> > header files for arrays defined in the complex types. But actually
> that
> > array represents a simple type and therefore it will not generate
> > separate class for that type. Then it will give errors at the
> > compilation since it can't find the particular header file.
> >
> > For example ;
> >
> > <s:complexType name="Thing" final="restriction">
> > <s:sequence>
> > <s:element ref="s0:aThing" minOccurs="0" maxOccurs="unbounded"/>
> > <s:element ref="s0:otherData" minOccurs="0"
> maxOccurs="unbounded"/>
> > </s:sequence>
> > </s:complexType>
> >
> > But actually aThing is a simple type
> >
> > <s:simpleType name="aThing">
> > <s:restriction base="s:string">
> > <s:maxLength value="255"/>
> > </s:restriction>
> > </s:simpleType>
> >
> > I have to work on this and have to stop the adding of lines to
include
> > the header files for arrays in complex types and those arrays are
> > actually simple types and that is defined in other place of the
wsdl.
> >
> > Thanks and regards,
> > Amila.
> >
> >
> >
> > > -----Original Message-----
> > > From: Amila Rathnayake [mailto:amilar@opensource.lk]
> > > Sent: Wednesday, August 04, 2004 3:39 PM
> > > To: 'Apache AXIS C Developers List'
> > > Subject: RE: Supporting for Non-Wrapped WSDL's
> > >
> > >
> > >
> > > Hi All,
> > >
> > > I regret to say that still nobody has commented on my issue and I
> > really
> > > want your comments on this to make sure that the generated code
for
> > > non-wrapped style is correct. I have generated both the server
side
> > and
> > > client side. I also checked the differences in generated codes for
> > > server and client sides in both wrapped and non-wrapped styles and
> it
> > > looks correct for me. But still your comments on this are really
> > > appreciated.
> > >
> > > I am sending the relevant diff file for the changes I've made on
> > > WSDL2Ws.java and you can apply this patch and test for non-wrapped
> > style
> > > wsdl's.
> > >
> > > With this change you can give a command line argument to generate
in
> > > non-wrapped style. If you don't give any command line argument for
> the
> > > wsdl2ws tool it will generate for wrapped style by default.
> > >
> > > For example for client side ;
> > >
> > > Java -classpath ./wsdl2ws.jar;%classpath%
> > > org.apache.axis.wsdl.wsdl2ws.WSDL2Ws <*.wsdl> -o./ClientOut -lc++
> > > -sclient -wnonwrapped
> > >
> > > -w wrapping style of the WSDL (wrapped|nonwrapped) - default is
> > wrapped
> > >
> > > Please try this out and send your comments.
> > >
> > > Thanks and Regards,
> > > Amila Rathnayake.
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: Amila Rathnayake [mailto:amilar@opensource.lk]
> > > > Sent: Tuesday, August 03, 2004 6:37 PM
> > > > To: 'Apache AXIS C Developers List'
> > > > Subject: RE: Supporting for Non-Wrapped WSDL's
> > > >
> > > >
> > > >
> > > >
> > > > Hi All,
> > > >
> > > > Theoretically it should be able to generate valid skeletons and
> > stubs
> > > in
> > > > the non-wrapped style by even using a wrapped style wsdl's.
> > > >
> > > > So that I have used a wrapped style wsdl and generated server
> > > skeletons
> > > > in the non-wrapped style.
> > > >
> > > > I have added the relevant wrapped style wsdl here with and
> following
> > > are
> > > > the differences between wrapped style code generation and
> > non-wrapped
> > > > style code generation by using the same wsdl file.
> > > >
> > > > Here I have given only the places where the generated code is
> > > different
> > > > in two styles. Except the following all the other files and
codes
> > > > generated by the wsdl2ws tool are same.
> > > >
> > > > By looking at the following codes you can find the differences
> > between
> > > > the code generation in two styles.
> > > >
> > > > thing.h and thing.cpp
> > > > ======================
> > > > in wrapped style
> > > > ------------------
> > > > void find_aThing(aThing Value0, AXIS_OUT_PARAM aThing_Array*
> > > OutValue0,
> > > > AXIS_OUT_PARAM otherData_Array* OutValue1);
> > > >
> > > > in the non-wrapped style
> > > > --------------------------
> > > > void find_aThing(find_aThing* Value0, AXIS_OUT_PARAM
aThing_Array*
> > > > OutValue0, AXIS_OUT_PARAM otherData_Array* OutValue1);
> > > >
> > > >
> > > > thingwrapper.cpp
> > > > ================
> > > > in wrapped style
> > > > ------------------
> > > > xsd__string v0 = pIWSDZ->getElementAsString("aThing",0);
> > > >
> > > > in the non-wrapped style
> > > > --------------------------
> > > > find_aThing *v0 =
> > > >
> > >
> >
>
(find_aThing*)pIWSDZ->getCmplxObject((void*)Axis_DeSerialize_find_aThing
> > > > , (void*)Axis_Create_find_aThing,
> > > > (void*)Axis_Delete_find_aThing
> > > > , "find_aThing", Axis_URI_find_aThing);
> > > >
> > > >
> > > > Please have a look at those differences with the attached wsdl
and
> > > > comment on this.
> > > >
> > > > Thanks and Regards,
> > > > Amila Rathnayake.
> > > >
> > > >
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: Amila Rathnayake [mailto:amilar@opensource.lk]
> > > > > Sent: Tuesday, August 03, 2004 5:40 PM
> > > > > To: 'Apache AXIS C Developers List'; axis-c-user@ws.apache.org
> > > > > Subject: RE: Supporting for Non-Wrapped WSDL's
> > > > >
> > > > > Hi All,
> > > > >
> > > > > Right now Axis C++ is supporting for wrapped style WSDL files.
> > > > > Non-wrapped style WSDL 's are not supported and currently all
> the
> > > > > doc-lit WSDL's are considered as wrapped style by default and
> > > > generating
> > > > > the Skeletons and Stubs accordingly by the WSDL2WS tool.
> > > > >
> > > > > I have implemented the support for non-wrapped style wsdl. But
> for
> > > > > testing purposes I need several valid WSDL's of non-wrapped
> style.
> > > > >
> > > > > I've found a simple WSDL which is in non-wrapped style. But
that
> > > WSDL
> > > > is
> > > > > having more than one part in the message. Then this should be
an
> > > > invalid
> > > > > wsdl since in the doc-lit type we can have only one part in
the
> > > > message.
> > > > >
> > > > > <wsdl:message name="loadXMLDataRequest">
> > > > >
> > > > > <wsdl:part name="in0" element="impl:in0"/>
> > > > >
> > > > > <wsdl:part name="in1" element="impl:in1"/>
> > > > >
> > > > > </wsdl:message>
> > > > >
> > > > > I have attached the relevant WSDL file here with.
> > > > >
> > > > > If you have any idea, please comment on this.
> > > > >
> > > > > Btw if you have come across any non-wrapped style wsdl file,
> > please
> > > > send
> > > > > that file.
> > > > >
> > > > > Thanks and Regards,
> > > > > Amila Rathnayake.
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: amilar@opensource.lk [mailto:amilar@opensource.lk]
> > > > > > Sent: Wednesday, July 21, 2004 6:31 PM
> > > > > > To: Apache AXIS C Developers List
> > > > > > Subject: Supporting for Non-Wrapped WSDL's
> > > > > >
> > > > > > Hi All,
> > > > > >
> > > > > > At this moment Axis is assuming and supporting only for
> Wrapped
> > > > style
> > > > > > WSDL's.
> > > > > >
> > > > > > In wrapped style WSDL's, all method parameters are wrapped
> > inside
> > > an
> > > > > > element named as the same name as operation and of the type
of
> > > > > > xsd:complextype.
> > > > > >
> > > > > > Ex: Wrapped Style
> > > > > > -----------------
> > > > > >
> > > > > > ...
> > > > > > <types>
> > > > > > <xsd:schema targetNamespace="http://www.sample.org/" >
> > > > > > <xsd:element name="countWords">
> > > > > > <xsd:complexType>
> > > > > > <xsd:sequence>
> > > > > > <xsd:element name="words"
> type="xsd:string"
> > />
> > > > > > </xsd:sequence>
> > > > > > </xsd:complexType>
> > > > > > </xsd:element>
> > > > > > </xsd:schema>
> > > > > > </types>
> > > > > > <message name="countWordsInput">
> > > > > > <part name="iInputText" element="tns:countWords" />
> > > > > > </message>
> > > > > > ...
> > > > > >
> > > > > > non-wrapped style
> > > > > > =================
> > > > > > But in Non-Wrapped style type is declared in the element
tag.
> > > > > > If you have overloaded operations, you cannot use the
> > > > document/literal
> > > > > > wrapped style.
> > > > > > WSDL allows overloaded operations. But when you add the
> wrapped
> > > > > pattern to
> > > > > > WSDL you require an element to have the same name as the
> > > operation,
> > > > > and
> > > > > > you cannot have two elements with the same name in XML. So
you
> > > must
> > > > > use
> > > > > > the document/literal, non-wrapped style or one of the RPC
> styles
> > > > > >
> > > > > > Eg: non-wrapped style
> > > > > > ----------------------
> > > > > >
> > > > > > ...
> > > > > > <types>
> > > > > > <xsd:schema targetNamespace="http://www.sample.org/" >
> > > > > > <xsd:element name="countWords" type="xsd:string" />
> > > > > > </xsd:schema>
> > > > > > </types>
> > > > > > <message name="countWordsInput">
> > > > > > <part name="iInputText" element="tns:countWords" />
> > > > > > </message>
> > > > > > ...
> > > > > >
> > > > > > Currently I am working on this and implementing the support
> for
> > > > > > non-wrapped style wsdl's.
> > > > > >
> > > > > > Regards,
> > > > > > Amila Rathnayake.
> > > > > >
> > > > > >
> >
RE: Supporting for Non-Wrapped WSDL's
Posted by Amila Rathnayake <am...@opensource.lk>.
Hi All,
I have amended the GatewayWebService.wsdl that I've sent you early and
make it a valid non-wrapped wsdl. The earlier one had 2 parts in a
message body.
Here I am sending the new wsdl and can somebody check this and say
whether this is a valid wsdl.
I have generated the server side and client side by using the latest
axis jars and with -wnonwrapped command line option. The generated code
seems to be ok. I compiled the server and client as well and it compiled
without any errors.
Thanks and Regards,
Amila Rathnayake.
> -----Original Message-----
> From: Amila Rathnayake [mailto:amilar@opensource.lk]
> Sent: Wednesday, August 04, 2004 6:33 PM
> To: 'Apache AXIS C Developers List'
> Cc: sanjiva@opensource.lk
> Subject: RE: Supporting for Non-Wrapped WSDL's
>
>
>
> Hi All,
>
> I still have two problems to clarify with my implementation of
> non-wrapped style wsdl support.
>
>
> 1).
>
> Theoretically in wrapped style wsdl's we can have same name for
> operation name and parameter name for that operation. But if we have
the
> same name for operation and parameter in non-wrapped wsdl, is it a
> valid/correct wsdl?
>
> Please clarify me if anybody has an idea on this.
>
>
> 2).
>
> In the stub header at the client side, it adds the code for include
> header files for arrays defined in the complex types. But actually
that
> array represents a simple type and therefore it will not generate
> separate class for that type. Then it will give errors at the
> compilation since it can't find the particular header file.
>
> For example ;
>
> <s:complexType name="Thing" final="restriction">
> <s:sequence>
> <s:element ref="s0:aThing" minOccurs="0" maxOccurs="unbounded"/>
> <s:element ref="s0:otherData" minOccurs="0"
maxOccurs="unbounded"/>
> </s:sequence>
> </s:complexType>
>
> But actually aThing is a simple type
>
> <s:simpleType name="aThing">
> <s:restriction base="s:string">
> <s:maxLength value="255"/>
> </s:restriction>
> </s:simpleType>
>
> I have to work on this and have to stop the adding of lines to include
> the header files for arrays in complex types and those arrays are
> actually simple types and that is defined in other place of the wsdl.
>
> Thanks and regards,
> Amila.
>
>
>
> > -----Original Message-----
> > From: Amila Rathnayake [mailto:amilar@opensource.lk]
> > Sent: Wednesday, August 04, 2004 3:39 PM
> > To: 'Apache AXIS C Developers List'
> > Subject: RE: Supporting for Non-Wrapped WSDL's
> >
> >
> >
> > Hi All,
> >
> > I regret to say that still nobody has commented on my issue and I
> really
> > want your comments on this to make sure that the generated code for
> > non-wrapped style is correct. I have generated both the server side
> and
> > client side. I also checked the differences in generated codes for
> > server and client sides in both wrapped and non-wrapped styles and
it
> > looks correct for me. But still your comments on this are really
> > appreciated.
> >
> > I am sending the relevant diff file for the changes I've made on
> > WSDL2Ws.java and you can apply this patch and test for non-wrapped
> style
> > wsdl's.
> >
> > With this change you can give a command line argument to generate in
> > non-wrapped style. If you don't give any command line argument for
the
> > wsdl2ws tool it will generate for wrapped style by default.
> >
> > For example for client side ;
> >
> > Java -classpath ./wsdl2ws.jar;%classpath%
> > org.apache.axis.wsdl.wsdl2ws.WSDL2Ws <*.wsdl> -o./ClientOut -lc++
> > -sclient -wnonwrapped
> >
> > -w wrapping style of the WSDL (wrapped|nonwrapped) - default is
> wrapped
> >
> > Please try this out and send your comments.
> >
> > Thanks and Regards,
> > Amila Rathnayake.
> >
> >
> >
> > > -----Original Message-----
> > > From: Amila Rathnayake [mailto:amilar@opensource.lk]
> > > Sent: Tuesday, August 03, 2004 6:37 PM
> > > To: 'Apache AXIS C Developers List'
> > > Subject: RE: Supporting for Non-Wrapped WSDL's
> > >
> > >
> > >
> > >
> > > Hi All,
> > >
> > > Theoretically it should be able to generate valid skeletons and
> stubs
> > in
> > > the non-wrapped style by even using a wrapped style wsdl's.
> > >
> > > So that I have used a wrapped style wsdl and generated server
> > skeletons
> > > in the non-wrapped style.
> > >
> > > I have added the relevant wrapped style wsdl here with and
following
> > are
> > > the differences between wrapped style code generation and
> non-wrapped
> > > style code generation by using the same wsdl file.
> > >
> > > Here I have given only the places where the generated code is
> > different
> > > in two styles. Except the following all the other files and codes
> > > generated by the wsdl2ws tool are same.
> > >
> > > By looking at the following codes you can find the differences
> between
> > > the code generation in two styles.
> > >
> > > thing.h and thing.cpp
> > > ======================
> > > in wrapped style
> > > ------------------
> > > void find_aThing(aThing Value0, AXIS_OUT_PARAM aThing_Array*
> > OutValue0,
> > > AXIS_OUT_PARAM otherData_Array* OutValue1);
> > >
> > > in the non-wrapped style
> > > --------------------------
> > > void find_aThing(find_aThing* Value0, AXIS_OUT_PARAM aThing_Array*
> > > OutValue0, AXIS_OUT_PARAM otherData_Array* OutValue1);
> > >
> > >
> > > thingwrapper.cpp
> > > ================
> > > in wrapped style
> > > ------------------
> > > xsd__string v0 = pIWSDZ->getElementAsString("aThing",0);
> > >
> > > in the non-wrapped style
> > > --------------------------
> > > find_aThing *v0 =
> > >
> >
>
(find_aThing*)pIWSDZ->getCmplxObject((void*)Axis_DeSerialize_find_aThing
> > > , (void*)Axis_Create_find_aThing,
> > > (void*)Axis_Delete_find_aThing
> > > , "find_aThing", Axis_URI_find_aThing);
> > >
> > >
> > > Please have a look at those differences with the attached wsdl and
> > > comment on this.
> > >
> > > Thanks and Regards,
> > > Amila Rathnayake.
> > >
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: Amila Rathnayake [mailto:amilar@opensource.lk]
> > > > Sent: Tuesday, August 03, 2004 5:40 PM
> > > > To: 'Apache AXIS C Developers List'; axis-c-user@ws.apache.org
> > > > Subject: RE: Supporting for Non-Wrapped WSDL's
> > > >
> > > > Hi All,
> > > >
> > > > Right now Axis C++ is supporting for wrapped style WSDL files.
> > > > Non-wrapped style WSDL 's are not supported and currently all
the
> > > > doc-lit WSDL's are considered as wrapped style by default and
> > > generating
> > > > the Skeletons and Stubs accordingly by the WSDL2WS tool.
> > > >
> > > > I have implemented the support for non-wrapped style wsdl. But
for
> > > > testing purposes I need several valid WSDL's of non-wrapped
style.
> > > >
> > > > I've found a simple WSDL which is in non-wrapped style. But that
> > WSDL
> > > is
> > > > having more than one part in the message. Then this should be an
> > > invalid
> > > > wsdl since in the doc-lit type we can have only one part in the
> > > message.
> > > >
> > > > <wsdl:message name="loadXMLDataRequest">
> > > >
> > > > <wsdl:part name="in0" element="impl:in0"/>
> > > >
> > > > <wsdl:part name="in1" element="impl:in1"/>
> > > >
> > > > </wsdl:message>
> > > >
> > > > I have attached the relevant WSDL file here with.
> > > >
> > > > If you have any idea, please comment on this.
> > > >
> > > > Btw if you have come across any non-wrapped style wsdl file,
> please
> > > send
> > > > that file.
> > > >
> > > > Thanks and Regards,
> > > > Amila Rathnayake.
> > > >
> > > >
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: amilar@opensource.lk [mailto:amilar@opensource.lk]
> > > > > Sent: Wednesday, July 21, 2004 6:31 PM
> > > > > To: Apache AXIS C Developers List
> > > > > Subject: Supporting for Non-Wrapped WSDL's
> > > > >
> > > > > Hi All,
> > > > >
> > > > > At this moment Axis is assuming and supporting only for
Wrapped
> > > style
> > > > > WSDL's.
> > > > >
> > > > > In wrapped style WSDL's, all method parameters are wrapped
> inside
> > an
> > > > > element named as the same name as operation and of the type of
> > > > > xsd:complextype.
> > > > >
> > > > > Ex: Wrapped Style
> > > > > -----------------
> > > > >
> > > > > ...
> > > > > <types>
> > > > > <xsd:schema targetNamespace="http://www.sample.org/" >
> > > > > <xsd:element name="countWords">
> > > > > <xsd:complexType>
> > > > > <xsd:sequence>
> > > > > <xsd:element name="words"
type="xsd:string"
> />
> > > > > </xsd:sequence>
> > > > > </xsd:complexType>
> > > > > </xsd:element>
> > > > > </xsd:schema>
> > > > > </types>
> > > > > <message name="countWordsInput">
> > > > > <part name="iInputText" element="tns:countWords" />
> > > > > </message>
> > > > > ...
> > > > >
> > > > > non-wrapped style
> > > > > =================
> > > > > But in Non-Wrapped style type is declared in the element tag.
> > > > > If you have overloaded operations, you cannot use the
> > > document/literal
> > > > > wrapped style.
> > > > > WSDL allows overloaded operations. But when you add the
wrapped
> > > > pattern to
> > > > > WSDL you require an element to have the same name as the
> > operation,
> > > > and
> > > > > you cannot have two elements with the same name in XML. So you
> > must
> > > > use
> > > > > the document/literal, non-wrapped style or one of the RPC
styles
> > > > >
> > > > > Eg: non-wrapped style
> > > > > ----------------------
> > > > >
> > > > > ...
> > > > > <types>
> > > > > <xsd:schema targetNamespace="http://www.sample.org/" >
> > > > > <xsd:element name="countWords" type="xsd:string" />
> > > > > </xsd:schema>
> > > > > </types>
> > > > > <message name="countWordsInput">
> > > > > <part name="iInputText" element="tns:countWords" />
> > > > > </message>
> > > > > ...
> > > > >
> > > > > Currently I am working on this and implementing the support
for
> > > > > non-wrapped style wsdl's.
> > > > >
> > > > > Regards,
> > > > > Amila Rathnayake.
> > > > >
> > > > >
>
RE: Supporting for Non-Wrapped WSDL's
Posted by Amila Rathnayake <am...@opensource.lk>.
Hi All,
I have amended the GatewayWebService.wsdl that I've sent you early and
make it a valid non-wrapped wsdl. The earlier one had 2 parts in a
message body.
Here I am sending the new wsdl and can somebody check this and say
whether this is a valid wsdl.
I have generated the server side and client side by using the latest
axis jars and with -wnonwrapped command line option. The generated code
seems to be ok. I compiled the server and client as well and it compiled
without any errors.
Thanks and Regards,
Amila Rathnayake.
> -----Original Message-----
> From: Amila Rathnayake [mailto:amilar@opensource.lk]
> Sent: Wednesday, August 04, 2004 6:33 PM
> To: 'Apache AXIS C Developers List'
> Cc: sanjiva@opensource.lk
> Subject: RE: Supporting for Non-Wrapped WSDL's
>
>
>
> Hi All,
>
> I still have two problems to clarify with my implementation of
> non-wrapped style wsdl support.
>
>
> 1).
>
> Theoretically in wrapped style wsdl's we can have same name for
> operation name and parameter name for that operation. But if we have
the
> same name for operation and parameter in non-wrapped wsdl, is it a
> valid/correct wsdl?
>
> Please clarify me if anybody has an idea on this.
>
>
> 2).
>
> In the stub header at the client side, it adds the code for include
> header files for arrays defined in the complex types. But actually
that
> array represents a simple type and therefore it will not generate
> separate class for that type. Then it will give errors at the
> compilation since it can't find the particular header file.
>
> For example ;
>
> <s:complexType name="Thing" final="restriction">
> <s:sequence>
> <s:element ref="s0:aThing" minOccurs="0" maxOccurs="unbounded"/>
> <s:element ref="s0:otherData" minOccurs="0"
maxOccurs="unbounded"/>
> </s:sequence>
> </s:complexType>
>
> But actually aThing is a simple type
>
> <s:simpleType name="aThing">
> <s:restriction base="s:string">
> <s:maxLength value="255"/>
> </s:restriction>
> </s:simpleType>
>
> I have to work on this and have to stop the adding of lines to include
> the header files for arrays in complex types and those arrays are
> actually simple types and that is defined in other place of the wsdl.
>
> Thanks and regards,
> Amila.
>
>
>
> > -----Original Message-----
> > From: Amila Rathnayake [mailto:amilar@opensource.lk]
> > Sent: Wednesday, August 04, 2004 3:39 PM
> > To: 'Apache AXIS C Developers List'
> > Subject: RE: Supporting for Non-Wrapped WSDL's
> >
> >
> >
> > Hi All,
> >
> > I regret to say that still nobody has commented on my issue and I
> really
> > want your comments on this to make sure that the generated code for
> > non-wrapped style is correct. I have generated both the server side
> and
> > client side. I also checked the differences in generated codes for
> > server and client sides in both wrapped and non-wrapped styles and
it
> > looks correct for me. But still your comments on this are really
> > appreciated.
> >
> > I am sending the relevant diff file for the changes I've made on
> > WSDL2Ws.java and you can apply this patch and test for non-wrapped
> style
> > wsdl's.
> >
> > With this change you can give a command line argument to generate in
> > non-wrapped style. If you don't give any command line argument for
the
> > wsdl2ws tool it will generate for wrapped style by default.
> >
> > For example for client side ;
> >
> > Java -classpath ./wsdl2ws.jar;%classpath%
> > org.apache.axis.wsdl.wsdl2ws.WSDL2Ws <*.wsdl> -o./ClientOut -lc++
> > -sclient -wnonwrapped
> >
> > -w wrapping style of the WSDL (wrapped|nonwrapped) - default is
> wrapped
> >
> > Please try this out and send your comments.
> >
> > Thanks and Regards,
> > Amila Rathnayake.
> >
> >
> >
> > > -----Original Message-----
> > > From: Amila Rathnayake [mailto:amilar@opensource.lk]
> > > Sent: Tuesday, August 03, 2004 6:37 PM
> > > To: 'Apache AXIS C Developers List'
> > > Subject: RE: Supporting for Non-Wrapped WSDL's
> > >
> > >
> > >
> > >
> > > Hi All,
> > >
> > > Theoretically it should be able to generate valid skeletons and
> stubs
> > in
> > > the non-wrapped style by even using a wrapped style wsdl's.
> > >
> > > So that I have used a wrapped style wsdl and generated server
> > skeletons
> > > in the non-wrapped style.
> > >
> > > I have added the relevant wrapped style wsdl here with and
following
> > are
> > > the differences between wrapped style code generation and
> non-wrapped
> > > style code generation by using the same wsdl file.
> > >
> > > Here I have given only the places where the generated code is
> > different
> > > in two styles. Except the following all the other files and codes
> > > generated by the wsdl2ws tool are same.
> > >
> > > By looking at the following codes you can find the differences
> between
> > > the code generation in two styles.
> > >
> > > thing.h and thing.cpp
> > > ======================
> > > in wrapped style
> > > ------------------
> > > void find_aThing(aThing Value0, AXIS_OUT_PARAM aThing_Array*
> > OutValue0,
> > > AXIS_OUT_PARAM otherData_Array* OutValue1);
> > >
> > > in the non-wrapped style
> > > --------------------------
> > > void find_aThing(find_aThing* Value0, AXIS_OUT_PARAM aThing_Array*
> > > OutValue0, AXIS_OUT_PARAM otherData_Array* OutValue1);
> > >
> > >
> > > thingwrapper.cpp
> > > ================
> > > in wrapped style
> > > ------------------
> > > xsd__string v0 = pIWSDZ->getElementAsString("aThing",0);
> > >
> > > in the non-wrapped style
> > > --------------------------
> > > find_aThing *v0 =
> > >
> >
>
(find_aThing*)pIWSDZ->getCmplxObject((void*)Axis_DeSerialize_find_aThing
> > > , (void*)Axis_Create_find_aThing,
> > > (void*)Axis_Delete_find_aThing
> > > , "find_aThing", Axis_URI_find_aThing);
> > >
> > >
> > > Please have a look at those differences with the attached wsdl and
> > > comment on this.
> > >
> > > Thanks and Regards,
> > > Amila Rathnayake.
> > >
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: Amila Rathnayake [mailto:amilar@opensource.lk]
> > > > Sent: Tuesday, August 03, 2004 5:40 PM
> > > > To: 'Apache AXIS C Developers List'; axis-c-user@ws.apache.org
> > > > Subject: RE: Supporting for Non-Wrapped WSDL's
> > > >
> > > > Hi All,
> > > >
> > > > Right now Axis C++ is supporting for wrapped style WSDL files.
> > > > Non-wrapped style WSDL 's are not supported and currently all
the
> > > > doc-lit WSDL's are considered as wrapped style by default and
> > > generating
> > > > the Skeletons and Stubs accordingly by the WSDL2WS tool.
> > > >
> > > > I have implemented the support for non-wrapped style wsdl. But
for
> > > > testing purposes I need several valid WSDL's of non-wrapped
style.
> > > >
> > > > I've found a simple WSDL which is in non-wrapped style. But that
> > WSDL
> > > is
> > > > having more than one part in the message. Then this should be an
> > > invalid
> > > > wsdl since in the doc-lit type we can have only one part in the
> > > message.
> > > >
> > > > <wsdl:message name="loadXMLDataRequest">
> > > >
> > > > <wsdl:part name="in0" element="impl:in0"/>
> > > >
> > > > <wsdl:part name="in1" element="impl:in1"/>
> > > >
> > > > </wsdl:message>
> > > >
> > > > I have attached the relevant WSDL file here with.
> > > >
> > > > If you have any idea, please comment on this.
> > > >
> > > > Btw if you have come across any non-wrapped style wsdl file,
> please
> > > send
> > > > that file.
> > > >
> > > > Thanks and Regards,
> > > > Amila Rathnayake.
> > > >
> > > >
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: amilar@opensource.lk [mailto:amilar@opensource.lk]
> > > > > Sent: Wednesday, July 21, 2004 6:31 PM
> > > > > To: Apache AXIS C Developers List
> > > > > Subject: Supporting for Non-Wrapped WSDL's
> > > > >
> > > > > Hi All,
> > > > >
> > > > > At this moment Axis is assuming and supporting only for
Wrapped
> > > style
> > > > > WSDL's.
> > > > >
> > > > > In wrapped style WSDL's, all method parameters are wrapped
> inside
> > an
> > > > > element named as the same name as operation and of the type of
> > > > > xsd:complextype.
> > > > >
> > > > > Ex: Wrapped Style
> > > > > -----------------
> > > > >
> > > > > ...
> > > > > <types>
> > > > > <xsd:schema targetNamespace="http://www.sample.org/" >
> > > > > <xsd:element name="countWords">
> > > > > <xsd:complexType>
> > > > > <xsd:sequence>
> > > > > <xsd:element name="words"
type="xsd:string"
> />
> > > > > </xsd:sequence>
> > > > > </xsd:complexType>
> > > > > </xsd:element>
> > > > > </xsd:schema>
> > > > > </types>
> > > > > <message name="countWordsInput">
> > > > > <part name="iInputText" element="tns:countWords" />
> > > > > </message>
> > > > > ...
> > > > >
> > > > > non-wrapped style
> > > > > =================
> > > > > But in Non-Wrapped style type is declared in the element tag.
> > > > > If you have overloaded operations, you cannot use the
> > > document/literal
> > > > > wrapped style.
> > > > > WSDL allows overloaded operations. But when you add the
wrapped
> > > > pattern to
> > > > > WSDL you require an element to have the same name as the
> > operation,
> > > > and
> > > > > you cannot have two elements with the same name in XML. So you
> > must
> > > > use
> > > > > the document/literal, non-wrapped style or one of the RPC
styles
> > > > >
> > > > > Eg: non-wrapped style
> > > > > ----------------------
> > > > >
> > > > > ...
> > > > > <types>
> > > > > <xsd:schema targetNamespace="http://www.sample.org/" >
> > > > > <xsd:element name="countWords" type="xsd:string" />
> > > > > </xsd:schema>
> > > > > </types>
> > > > > <message name="countWordsInput">
> > > > > <part name="iInputText" element="tns:countWords" />
> > > > > </message>
> > > > > ...
> > > > >
> > > > > Currently I am working on this and implementing the support
for
> > > > > non-wrapped style wsdl's.
> > > > >
> > > > > Regards,
> > > > > Amila Rathnayake.
> > > > >
> > > > >
>
RE: Supporting for Non-Wrapped WSDL's
Posted by Amila Rathnayake <am...@opensource.lk>.
Hi All,
I still have two problems to clarify with my implementation of
non-wrapped style wsdl support.
1).
Theoretically in wrapped style wsdl's we can have same name for
operation name and parameter name for that operation. But if we have the
same name for operation and parameter in non-wrapped wsdl, is it a
valid/correct wsdl?
Please clarify me if anybody has an idea on this.
2).
In the stub header at the client side, it adds the code for include
header files for arrays defined in the complex types. But actually that
array represents a simple type and therefore it will not generate
separate class for that type. Then it will give errors at the
compilation since it can't find the particular header file.
For example ;
<s:complexType name="Thing" final="restriction">
<s:sequence>
<s:element ref="s0:aThing" minOccurs="0" maxOccurs="unbounded"/>
<s:element ref="s0:otherData" minOccurs="0" maxOccurs="unbounded"/>
</s:sequence>
</s:complexType>
But actually aThing is a simple type
<s:simpleType name="aThing">
<s:restriction base="s:string">
<s:maxLength value="255"/>
</s:restriction>
</s:simpleType>
I have to work on this and have to stop the adding of lines to include
the header files for arrays in complex types and those arrays are
actually simple types and that is defined in other place of the wsdl.
Thanks and regards,
Amila.
> -----Original Message-----
> From: Amila Rathnayake [mailto:amilar@opensource.lk]
> Sent: Wednesday, August 04, 2004 3:39 PM
> To: 'Apache AXIS C Developers List'
> Subject: RE: Supporting for Non-Wrapped WSDL's
>
>
>
> Hi All,
>
> I regret to say that still nobody has commented on my issue and I
really
> want your comments on this to make sure that the generated code for
> non-wrapped style is correct. I have generated both the server side
and
> client side. I also checked the differences in generated codes for
> server and client sides in both wrapped and non-wrapped styles and it
> looks correct for me. But still your comments on this are really
> appreciated.
>
> I am sending the relevant diff file for the changes I've made on
> WSDL2Ws.java and you can apply this patch and test for non-wrapped
style
> wsdl's.
>
> With this change you can give a command line argument to generate in
> non-wrapped style. If you don't give any command line argument for the
> wsdl2ws tool it will generate for wrapped style by default.
>
> For example for client side ;
>
> Java -classpath ./wsdl2ws.jar;%classpath%
> org.apache.axis.wsdl.wsdl2ws.WSDL2Ws <*.wsdl> -o./ClientOut -lc++
> -sclient -wnonwrapped
>
> -w wrapping style of the WSDL (wrapped|nonwrapped) - default is
wrapped
>
> Please try this out and send your comments.
>
> Thanks and Regards,
> Amila Rathnayake.
>
>
>
> > -----Original Message-----
> > From: Amila Rathnayake [mailto:amilar@opensource.lk]
> > Sent: Tuesday, August 03, 2004 6:37 PM
> > To: 'Apache AXIS C Developers List'
> > Subject: RE: Supporting for Non-Wrapped WSDL's
> >
> >
> >
> >
> > Hi All,
> >
> > Theoretically it should be able to generate valid skeletons and
stubs
> in
> > the non-wrapped style by even using a wrapped style wsdl's.
> >
> > So that I have used a wrapped style wsdl and generated server
> skeletons
> > in the non-wrapped style.
> >
> > I have added the relevant wrapped style wsdl here with and following
> are
> > the differences between wrapped style code generation and
non-wrapped
> > style code generation by using the same wsdl file.
> >
> > Here I have given only the places where the generated code is
> different
> > in two styles. Except the following all the other files and codes
> > generated by the wsdl2ws tool are same.
> >
> > By looking at the following codes you can find the differences
between
> > the code generation in two styles.
> >
> > thing.h and thing.cpp
> > ======================
> > in wrapped style
> > ------------------
> > void find_aThing(aThing Value0, AXIS_OUT_PARAM aThing_Array*
> OutValue0,
> > AXIS_OUT_PARAM otherData_Array* OutValue1);
> >
> > in the non-wrapped style
> > --------------------------
> > void find_aThing(find_aThing* Value0, AXIS_OUT_PARAM aThing_Array*
> > OutValue0, AXIS_OUT_PARAM otherData_Array* OutValue1);
> >
> >
> > thingwrapper.cpp
> > ================
> > in wrapped style
> > ------------------
> > xsd__string v0 = pIWSDZ->getElementAsString("aThing",0);
> >
> > in the non-wrapped style
> > --------------------------
> > find_aThing *v0 =
> >
>
(find_aThing*)pIWSDZ->getCmplxObject((void*)Axis_DeSerialize_find_aThing
> > , (void*)Axis_Create_find_aThing,
> > (void*)Axis_Delete_find_aThing
> > , "find_aThing", Axis_URI_find_aThing);
> >
> >
> > Please have a look at those differences with the attached wsdl and
> > comment on this.
> >
> > Thanks and Regards,
> > Amila Rathnayake.
> >
> >
> >
> >
> > > -----Original Message-----
> > > From: Amila Rathnayake [mailto:amilar@opensource.lk]
> > > Sent: Tuesday, August 03, 2004 5:40 PM
> > > To: 'Apache AXIS C Developers List'; axis-c-user@ws.apache.org
> > > Subject: RE: Supporting for Non-Wrapped WSDL's
> > >
> > > Hi All,
> > >
> > > Right now Axis C++ is supporting for wrapped style WSDL files.
> > > Non-wrapped style WSDL 's are not supported and currently all the
> > > doc-lit WSDL's are considered as wrapped style by default and
> > generating
> > > the Skeletons and Stubs accordingly by the WSDL2WS tool.
> > >
> > > I have implemented the support for non-wrapped style wsdl. But for
> > > testing purposes I need several valid WSDL's of non-wrapped style.
> > >
> > > I've found a simple WSDL which is in non-wrapped style. But that
> WSDL
> > is
> > > having more than one part in the message. Then this should be an
> > invalid
> > > wsdl since in the doc-lit type we can have only one part in the
> > message.
> > >
> > > <wsdl:message name="loadXMLDataRequest">
> > >
> > > <wsdl:part name="in0" element="impl:in0"/>
> > >
> > > <wsdl:part name="in1" element="impl:in1"/>
> > >
> > > </wsdl:message>
> > >
> > > I have attached the relevant WSDL file here with.
> > >
> > > If you have any idea, please comment on this.
> > >
> > > Btw if you have come across any non-wrapped style wsdl file,
please
> > send
> > > that file.
> > >
> > > Thanks and Regards,
> > > Amila Rathnayake.
> > >
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: amilar@opensource.lk [mailto:amilar@opensource.lk]
> > > > Sent: Wednesday, July 21, 2004 6:31 PM
> > > > To: Apache AXIS C Developers List
> > > > Subject: Supporting for Non-Wrapped WSDL's
> > > >
> > > > Hi All,
> > > >
> > > > At this moment Axis is assuming and supporting only for Wrapped
> > style
> > > > WSDL's.
> > > >
> > > > In wrapped style WSDL's, all method parameters are wrapped
inside
> an
> > > > element named as the same name as operation and of the type of
> > > > xsd:complextype.
> > > >
> > > > Ex: Wrapped Style
> > > > -----------------
> > > >
> > > > ...
> > > > <types>
> > > > <xsd:schema targetNamespace="http://www.sample.org/" >
> > > > <xsd:element name="countWords">
> > > > <xsd:complexType>
> > > > <xsd:sequence>
> > > > <xsd:element name="words" type="xsd:string"
/>
> > > > </xsd:sequence>
> > > > </xsd:complexType>
> > > > </xsd:element>
> > > > </xsd:schema>
> > > > </types>
> > > > <message name="countWordsInput">
> > > > <part name="iInputText" element="tns:countWords" />
> > > > </message>
> > > > ...
> > > >
> > > > non-wrapped style
> > > > =================
> > > > But in Non-Wrapped style type is declared in the element tag.
> > > > If you have overloaded operations, you cannot use the
> > document/literal
> > > > wrapped style.
> > > > WSDL allows overloaded operations. But when you add the wrapped
> > > pattern to
> > > > WSDL you require an element to have the same name as the
> operation,
> > > and
> > > > you cannot have two elements with the same name in XML. So you
> must
> > > use
> > > > the document/literal, non-wrapped style or one of the RPC styles
> > > >
> > > > Eg: non-wrapped style
> > > > ----------------------
> > > >
> > > > ...
> > > > <types>
> > > > <xsd:schema targetNamespace="http://www.sample.org/" >
> > > > <xsd:element name="countWords" type="xsd:string" />
> > > > </xsd:schema>
> > > > </types>
> > > > <message name="countWordsInput">
> > > > <part name="iInputText" element="tns:countWords" />
> > > > </message>
> > > > ...
> > > >
> > > > Currently I am working on this and implementing the support for
> > > > non-wrapped style wsdl's.
> > > >
> > > > Regards,
> > > > Amila Rathnayake.
> > > >
> > > >
RE: Supporting for Non-Wrapped WSDL's
Posted by Amila Rathnayake <am...@opensource.lk>.
Hi All,
I regret to say that still nobody has commented on my issue and I really
want your comments on this to make sure that the generated code for
non-wrapped style is correct. I have generated both the server side and
client side. I also checked the differences in generated codes for
server and client sides in both wrapped and non-wrapped styles and it
looks correct for me. But still your comments on this are really
appreciated.
I am sending the relevant diff file for the changes I've made on
WSDL2Ws.java and you can apply this patch and test for non-wrapped style
wsdl's.
With this change you can give a command line argument to generate in
non-wrapped style. If you don't give any command line argument for the
wsdl2ws tool it will generate for wrapped style by default.
For example for client side ;
Java -classpath ./wsdl2ws.jar;%classpath%
org.apache.axis.wsdl.wsdl2ws.WSDL2Ws <*.wsdl> -o./ClientOut -lc++
-sclient -wnonwrapped
-w wrapping style of the WSDL (wrapped|nonwrapped) - default is wrapped
Please try this out and send your comments.
Thanks and Regards,
Amila Rathnayake.
> -----Original Message-----
> From: Amila Rathnayake [mailto:amilar@opensource.lk]
> Sent: Tuesday, August 03, 2004 6:37 PM
> To: 'Apache AXIS C Developers List'
> Subject: RE: Supporting for Non-Wrapped WSDL's
>
>
>
>
> Hi All,
>
> Theoretically it should be able to generate valid skeletons and stubs
in
> the non-wrapped style by even using a wrapped style wsdl's.
>
> So that I have used a wrapped style wsdl and generated server
skeletons
> in the non-wrapped style.
>
> I have added the relevant wrapped style wsdl here with and following
are
> the differences between wrapped style code generation and non-wrapped
> style code generation by using the same wsdl file.
>
> Here I have given only the places where the generated code is
different
> in two styles. Except the following all the other files and codes
> generated by the wsdl2ws tool are same.
>
> By looking at the following codes you can find the differences between
> the code generation in two styles.
>
> thing.h and thing.cpp
> ======================
> in wrapped style
> ------------------
> void find_aThing(aThing Value0, AXIS_OUT_PARAM aThing_Array*
OutValue0,
> AXIS_OUT_PARAM otherData_Array* OutValue1);
>
> in the non-wrapped style
> --------------------------
> void find_aThing(find_aThing* Value0, AXIS_OUT_PARAM aThing_Array*
> OutValue0, AXIS_OUT_PARAM otherData_Array* OutValue1);
>
>
> thingwrapper.cpp
> ================
> in wrapped style
> ------------------
> xsd__string v0 = pIWSDZ->getElementAsString("aThing",0);
>
> in the non-wrapped style
> --------------------------
> find_aThing *v0 =
>
(find_aThing*)pIWSDZ->getCmplxObject((void*)Axis_DeSerialize_find_aThing
> , (void*)Axis_Create_find_aThing,
> (void*)Axis_Delete_find_aThing
> , "find_aThing", Axis_URI_find_aThing);
>
>
> Please have a look at those differences with the attached wsdl and
> comment on this.
>
> Thanks and Regards,
> Amila Rathnayake.
>
>
>
>
> > -----Original Message-----
> > From: Amila Rathnayake [mailto:amilar@opensource.lk]
> > Sent: Tuesday, August 03, 2004 5:40 PM
> > To: 'Apache AXIS C Developers List'; axis-c-user@ws.apache.org
> > Subject: RE: Supporting for Non-Wrapped WSDL's
> >
> > Hi All,
> >
> > Right now Axis C++ is supporting for wrapped style WSDL files.
> > Non-wrapped style WSDL 's are not supported and currently all the
> > doc-lit WSDL's are considered as wrapped style by default and
> generating
> > the Skeletons and Stubs accordingly by the WSDL2WS tool.
> >
> > I have implemented the support for non-wrapped style wsdl. But for
> > testing purposes I need several valid WSDL's of non-wrapped style.
> >
> > I've found a simple WSDL which is in non-wrapped style. But that
WSDL
> is
> > having more than one part in the message. Then this should be an
> invalid
> > wsdl since in the doc-lit type we can have only one part in the
> message.
> >
> > <wsdl:message name="loadXMLDataRequest">
> >
> > <wsdl:part name="in0" element="impl:in0"/>
> >
> > <wsdl:part name="in1" element="impl:in1"/>
> >
> > </wsdl:message>
> >
> > I have attached the relevant WSDL file here with.
> >
> > If you have any idea, please comment on this.
> >
> > Btw if you have come across any non-wrapped style wsdl file, please
> send
> > that file.
> >
> > Thanks and Regards,
> > Amila Rathnayake.
> >
> >
> >
> >
> > > -----Original Message-----
> > > From: amilar@opensource.lk [mailto:amilar@opensource.lk]
> > > Sent: Wednesday, July 21, 2004 6:31 PM
> > > To: Apache AXIS C Developers List
> > > Subject: Supporting for Non-Wrapped WSDL's
> > >
> > > Hi All,
> > >
> > > At this moment Axis is assuming and supporting only for Wrapped
> style
> > > WSDL's.
> > >
> > > In wrapped style WSDL's, all method parameters are wrapped inside
an
> > > element named as the same name as operation and of the type of
> > > xsd:complextype.
> > >
> > > Ex: Wrapped Style
> > > -----------------
> > >
> > > ...
> > > <types>
> > > <xsd:schema targetNamespace="http://www.sample.org/" >
> > > <xsd:element name="countWords">
> > > <xsd:complexType>
> > > <xsd:sequence>
> > > <xsd:element name="words" type="xsd:string" />
> > > </xsd:sequence>
> > > </xsd:complexType>
> > > </xsd:element>
> > > </xsd:schema>
> > > </types>
> > > <message name="countWordsInput">
> > > <part name="iInputText" element="tns:countWords" />
> > > </message>
> > > ...
> > >
> > > non-wrapped style
> > > =================
> > > But in Non-Wrapped style type is declared in the element tag.
> > > If you have overloaded operations, you cannot use the
> document/literal
> > > wrapped style.
> > > WSDL allows overloaded operations. But when you add the wrapped
> > pattern to
> > > WSDL you require an element to have the same name as the
operation,
> > and
> > > you cannot have two elements with the same name in XML. So you
must
> > use
> > > the document/literal, non-wrapped style or one of the RPC styles
> > >
> > > Eg: non-wrapped style
> > > ----------------------
> > >
> > > ...
> > > <types>
> > > <xsd:schema targetNamespace="http://www.sample.org/" >
> > > <xsd:element name="countWords" type="xsd:string" />
> > > </xsd:schema>
> > > </types>
> > > <message name="countWordsInput">
> > > <part name="iInputText" element="tns:countWords" />
> > > </message>
> > > ...
> > >
> > > Currently I am working on this and implementing the support for
> > > non-wrapped style wsdl's.
> > >
> > > Regards,
> > > Amila Rathnayake.
> > >
> > >
RE: Supporting for Non-Wrapped WSDL's
Posted by Amila Rathnayake <am...@opensource.lk>.
Hi All,
Theoretically it should be able to generate valid skeletons and stubs in
the non-wrapped style by even using a wrapped style wsdl's.
So that I have used a wrapped style wsdl and generated server skeletons
in the non-wrapped style.
I have added the relevant wrapped style wsdl here with and following are
the differences between wrapped style code generation and non-wrapped
style code generation by using the same wsdl file.
Here I have given only the places where the generated code is different
in two styles. Except the following all the other files and codes
generated by the wsdl2ws tool are same.
By looking at the following codes you can find the differences between
the code generation in two styles.
thing.h and thing.cpp
======================
in wrapped style
------------------
void find_aThing(aThing Value0, AXIS_OUT_PARAM aThing_Array* OutValue0,
AXIS_OUT_PARAM otherData_Array* OutValue1);
in the non-wrapped style
--------------------------
void find_aThing(find_aThing* Value0, AXIS_OUT_PARAM aThing_Array*
OutValue0, AXIS_OUT_PARAM otherData_Array* OutValue1);
thingwrapper.cpp
================
in wrapped style
------------------
xsd__string v0 = pIWSDZ->getElementAsString("aThing",0);
in the non-wrapped style
--------------------------
find_aThing *v0 =
(find_aThing*)pIWSDZ->getCmplxObject((void*)Axis_DeSerialize_find_aThing
, (void*)Axis_Create_find_aThing,
(void*)Axis_Delete_find_aThing
, "find_aThing", Axis_URI_find_aThing);
Please have a look at those differences with the attached wsdl and
comment on this.
Thanks and Regards,
Amila Rathnayake.
> -----Original Message-----
> From: Amila Rathnayake [mailto:amilar@opensource.lk]
> Sent: Tuesday, August 03, 2004 5:40 PM
> To: 'Apache AXIS C Developers List'; axis-c-user@ws.apache.org
> Subject: RE: Supporting for Non-Wrapped WSDL's
>
> Hi All,
>
> Right now Axis C++ is supporting for wrapped style WSDL files.
> Non-wrapped style WSDL 's are not supported and currently all the
> doc-lit WSDL's are considered as wrapped style by default and
generating
> the Skeletons and Stubs accordingly by the WSDL2WS tool.
>
> I have implemented the support for non-wrapped style wsdl. But for
> testing purposes I need several valid WSDL's of non-wrapped style.
>
> I've found a simple WSDL which is in non-wrapped style. But that WSDL
is
> having more than one part in the message. Then this should be an
invalid
> wsdl since in the doc-lit type we can have only one part in the
message.
>
> <wsdl:message name="loadXMLDataRequest">
>
> <wsdl:part name="in0" element="impl:in0"/>
>
> <wsdl:part name="in1" element="impl:in1"/>
>
> </wsdl:message>
>
> I have attached the relevant WSDL file here with.
>
> If you have any idea, please comment on this.
>
> Btw if you have come across any non-wrapped style wsdl file, please
send
> that file.
>
> Thanks and Regards,
> Amila Rathnayake.
>
>
>
>
> > -----Original Message-----
> > From: amilar@opensource.lk [mailto:amilar@opensource.lk]
> > Sent: Wednesday, July 21, 2004 6:31 PM
> > To: Apache AXIS C Developers List
> > Subject: Supporting for Non-Wrapped WSDL's
> >
> > Hi All,
> >
> > At this moment Axis is assuming and supporting only for Wrapped
style
> > WSDL's.
> >
> > In wrapped style WSDL's, all method parameters are wrapped inside an
> > element named as the same name as operation and of the type of
> > xsd:complextype.
> >
> > Ex: Wrapped Style
> > -----------------
> >
> > ...
> > <types>
> > <xsd:schema targetNamespace="http://www.sample.org/" >
> > <xsd:element name="countWords">
> > <xsd:complexType>
> > <xsd:sequence>
> > <xsd:element name="words" type="xsd:string" />
> > </xsd:sequence>
> > </xsd:complexType>
> > </xsd:element>
> > </xsd:schema>
> > </types>
> > <message name="countWordsInput">
> > <part name="iInputText" element="tns:countWords" />
> > </message>
> > ...
> >
> > non-wrapped style
> > =================
> > But in Non-Wrapped style type is declared in the element tag.
> > If you have overloaded operations, you cannot use the
document/literal
> > wrapped style.
> > WSDL allows overloaded operations. But when you add the wrapped
> pattern to
> > WSDL you require an element to have the same name as the operation,
> and
> > you cannot have two elements with the same name in XML. So you must
> use
> > the document/literal, non-wrapped style or one of the RPC styles
> >
> > Eg: non-wrapped style
> > ----------------------
> >
> > ...
> > <types>
> > <xsd:schema targetNamespace="http://www.sample.org/" >
> > <xsd:element name="countWords" type="xsd:string" />
> > </xsd:schema>
> > </types>
> > <message name="countWordsInput">
> > <part name="iInputText" element="tns:countWords" />
> > </message>
> > ...
> >
> > Currently I am working on this and implementing the support for
> > non-wrapped style wsdl's.
> >
> > Regards,
> > Amila Rathnayake.
> >
> >
RE: Supporting for Non-Wrapped WSDL's
Posted by Susantha Kumara <su...@opensource.lk>.
Hi Amila,
This wsdl you have used is rpc/encoded style WSDL. AFAIK
wrapped/unwrapped does not relate to rpc style wsdls.
Susantha
---
-----Original Message-----
From: Amila Rathnayake [mailto:amilar@opensource.lk]
Sent: Tuesday, August 10, 2004 5:23 PM
To: 'Apache AXIS C Developers List'
Subject: RE: Supporting for Non-Wrapped WSDL's
Hi All,
Last time I have sent an attachment with a compressed file which is big
in size. That is because it has included the Debug directory of the VC++
project as well. So I have recalled that mail and will send the
attachment again after removing that directory. Sorry for any
inconvenience caused in downloading that attachment.
Thanks,
Amila.
-----Original Message-----
From: Amila Rathnayake [mailto:amilar@opensource.lk]
Sent: Monday, August 09, 2004 7:28 PM
To: axis-c-dev@ws.apache.org
Subject: RE: Supporting for Non-Wrapped WSDL's
Hi,
Herewith I am sending another sample test project for testing the
support in non-wrapped style code generation for doc-lit wsdl's. Please
find the attached files with all the source and project files in
compressed format and the relevant simpleWS.wsdl file.
Please check this.
Thanks,
Amila.
-----Original Message-----
From: Samisa Abeysinghe [mailto:samisa_abeysinghe@yahoo.com]
Sent: Friday, August 06, 2004 10:24 PM
To: Apache AXIS C User List
Subject: RE: Supporting for Non-Wrapped WSDL's
Hi Amila,
Great stuff.
Thank you for the update.
Samisa...
Amila Rathnayake <am...@opensource.lk> wrote:
Hi Samisa,
I found one simple wsdl from the links given. Thank you for sending them
and I will be sending the VC++ sample test projects for this non-wrapped
support. The wsdl given in the other links are not that simple wsdl's
and therefore having lots of other complexities in them.
I've generated server and client for both simpleWS.wsdl and
GatewayWebService.wsdl that I have sent you earlier. The generated code
got compiled without any problems.
Thanks and Regards,
Amila Rathnayake.
> -----Original Message-----
> From: Samisa Abeysinghe [mailto:samisa_abeysinghe@yahoo.com]
> Sent: Thursday, August 05, 2004 4:15 PM
> To: Apache AXIS C User List; 'Apache AXIS C Developers List'
> Subject: RE: Supporting for Non-Wrapped WSDL's
>
> Hi Amila,
> Few places where I thik you can get the type of WSDLs you are
looking
> for.
> http://paracite.eprints.org/paracite.wsdl
> http://www.mail-archive.com/wsif-user@ws.apache.org/msg00420.html
> http://heasarc.gsfc.nasa.gov/itwg/wsdl_all.html
> http://www.freewebs.com/reude/simpleWS.wsdl
> http://www.mcdowall.com/wsdl/post-xmlstore.wsdl
> http://archives.us-vo.org/metadata/msg00378.html
> http://www.srdc.metu.edu.tr/~yavuz/MyAdmitVisit.wsdl
> http://www.srdc.metu.edu.tr/~yavuz/MyOrderEntry.wsdl
> http://www.intertwingly.net/stories/2002/03/05/weblogswsdl.html
> http://www.xmltoday.com/stock.wsdl
>
> Hope this helps.
> Thanks,
> Samisa...
>
>
>
> --- Amila Rathnayake wrote:
>
> > Hi All,
> >
> > Right now Axis C++ is supporting for wrapped style WSDL files.
> > Non-wrapped style WSDL 's are not supported and currently all the
> > doc-lit WSDL's are considered as wrapped style by default and
generating
> > the Skeletons and Stubs accordingly by the WSDL2WS tool.
> >
> > I have implemented the support for non-wrapped style wsdl. But for
> > testing purposes I need several valid WSDL's of non-wrapped style.
> >
> > I've found a simple WSDL which is in non-wrapped style. But that
WSDL is
> > having more than one part in the message. Then this should be an
invalid
> > wsdl since in the doc-lit type we can have only one part in the
message.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > I have attached the relevant WSDL file here with.
> >
> > If you have any idea, please comment on this.
> >
> > Btw if you have come across any non-wrapped style wsdl file, please
send
> > that file.
> >
> > Thanks and Regards,
> > Amila Rathnayake.
> >
> >
> >
> >
> > > -----Original Message-----
> > > From: amilar@opensource.lk [mailto:amilar@opensource.lk]
> > > Sent: Wednesday, July 21, 2004 6:31 PM
> > > To: Apache AXIS C Developers List
> > > Subject: Supporting for Non-Wrapped WSDL's
> > >
> > > Hi All,
> > >
> > > At this moment Axis is assuming and supporting only for Wrapped
style
> > > WSDL's.
> > >
> > > In wrapped style WSDL's, all method parameters are wrapped inside
an
> > > element named as the same name as operation and of the type of
> > > xsd:complextype.
> > >
> > > Ex: Wrapped Style
> > > -----------------
> > >
> > > ...
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > ...
> > >
> > > non-wrapped style
> > > =================
> > > But in Non-Wrapped style type is declared in the element tag.
> > > If you have overloaded operations, you cannot use the
document/literal
> > > wrapped style.
> > > WSDL allows overloaded operations. But when you add the wrapped
> > pattern to
> > > WSDL you require an element to have the same name as the
operation,
> > and
> > > you cannot have two elements with the same name in XML. So you
must
> > use
> > > the document/literal, non-wrapped style or one of the RPC styles
> > >
> > > Eg: non-wrapped style
> > > ----------------------
> > >
> > > ...
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > ...
> > >
> > > Currently I am working on this and implementing the support for
> > > non-wrapped style wsdl's.
> > >
> > > Regards,
> > > Amila Rathnayake.
> > >
> > >
> >
> >
>
> > ATTACHMENT part 2 application/octet-stream
name=GatewayWebService.wsdl
>
>
>
>
>
>
> __________________________________
> Do you Yahoo!?
> New and Improved Yahoo! Mail - 100MB free storage!
> http://promotions.yahoo.com/new_mail
_____
Do you Yahoo!?
Yahoo!
<http://us.rd.yahoo.com/mail_us/taglines/aac/*http:/promotions.yahoo.com
/new_mail/static/ease.html> Mail Address AutoComplete - You start. We
finish.
RE: Supporting for Non-Wrapped WSDL's
Posted by Amila Rathnayake <am...@opensource.lk>.
Hi All,
Last time I have sent an attachment with a compressed file which is big
in size. That is because it has included the Debug directory of the VC++
project as well. So I have recalled that mail and will send the
attachment again after removing that directory. Sorry for any
inconvenience caused in downloading that attachment.
Thanks,
Amila.
-----Original Message-----
From: Amila Rathnayake [mailto:amilar@opensource.lk]
Sent: Monday, August 09, 2004 7:28 PM
To: axis-c-dev@ws.apache.org
Subject: RE: Supporting for Non-Wrapped WSDL's
Hi,
Herewith I am sending another sample test project for testing the
support in non-wrapped style code generation for doc-lit wsdl's. Please
find the attached files with all the source and project files in
compressed format and the relevant simpleWS.wsdl file.
Please check this.
Thanks,
Amila.
-----Original Message-----
From: Samisa Abeysinghe [mailto:samisa_abeysinghe@yahoo.com]
Sent: Friday, August 06, 2004 10:24 PM
To: Apache AXIS C User List
Subject: RE: Supporting for Non-Wrapped WSDL's
Hi Amila,
Great stuff.
Thank you for the update.
Samisa...
Amila Rathnayake <am...@opensource.lk> wrote:
Hi Samisa,
I found one simple wsdl from the links given. Thank you for sending them
and I will be sending the VC++ sample test projects for this non-wrapped
support. The wsdl given in the other links are not that simple wsdl's
and therefore having lots of other complexities in them.
I've generated server and client for both simpleWS.wsdl and
GatewayWebService.wsdl that I have sent you earlier. The generated code
got compiled without any problems.
Thanks and Regards,
Amila Rathnayake.
> -----Original Message-----
> From: Samisa Abeysinghe [mailto:samisa_abeysinghe@yahoo.com]
> Sent: Thursday, August 05, 2004 4:15 PM
> To: Apache AXIS C User List; 'Apache AXIS C Developers List'
> Subject: RE: Supporting for Non-Wrapped WSDL's
>
> Hi Amila,
> Few places where I thik you can get the type of WSDLs you are
looking
> for.
> http://paracite.eprints.org/paracite.wsdl
> http://www.mail-archive.com/wsif-user@ws.apache.org/msg00420.html
> http://heasarc.gsfc.nasa.gov/itwg/wsdl_all.html
> http://www.freewebs.com/reude/simpleWS.wsdl
> http://www.mcdowall.com/wsdl/post-xmlstore.wsdl
> http://archives.us-vo.org/metadata/msg00378.html
> http://www.srdc.metu.edu.tr/~yavuz/MyAdmitVisit.wsdl
> http://www.srdc.metu.edu.tr/~yavuz/MyOrderEntry.wsdl
> http://www.intertwingly.net/stories/2002/03/05/weblogswsdl.html
> http://www.xmltoday.com/stock.wsdl
>
> Hope this helps.
> Thanks,
> Samisa...
>
>
>
> --- Amila Rathnayake wrote:
>
> > Hi All,
> >
> > Right now Axis C++ is supporting for wrapped style WSDL files.
> > Non-wrapped style WSDL 's are not supported and currently all the
> > doc-lit WSDL's are considered as wrapped style by default and
generating
> > the Skeletons and Stubs accordingly by the WSDL2WS tool.
> >
> > I have implemented the support for non-wrapped style wsdl. But for
> > testing purposes I need several valid WSDL's of non-wrapped style.
> >
> > I've found a simple WSDL which is in non-wrapped style. But that
WSDL is
> > having more than one part in the message. Then this should be an
invalid
> > wsdl since in the doc-lit type we can have only one part in the
message.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > I have attached the relevant WSDL file here with.
> >
> > If you have any idea, please comment on this.
> >
> > Btw if you have come across any non-wrapped style wsdl file, please
send
> > that file.
> >
> > Thanks and Regards,
> > Amila Rathnayake.
> >
> >
> >
> >
> > > -----Original Message-----
> > > From: amilar@opensource.lk [mailto:amilar@opensource.lk]
> > > Sent: Wednesday, July 21, 2004 6:31 PM
> > > To: Apache AXIS C Developers List
> > > Subject: Supporting for Non-Wrapped WSDL's
> > >
> > > Hi All,
> > >
> > > At this moment Axis is assuming and supporting only for Wrapped
style
> > > WSDL's.
> > >
> > > In wrapped style WSDL's, all method parameters are wrapped inside
an
> > > element named as the same name as operation and of the type of
> > > xsd:complextype.
> > >
> > > Ex: Wrapped Style
> > > -----------------
> > >
> > > ...
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > ...
> > >
> > > non-wrapped style
> > > =================
> > > But in Non-Wrapped style type is declared in the element tag.
> > > If you have overloaded operations, you cannot use the
document/literal
> > > wrapped style.
> > > WSDL allows overloaded operations. But when you add the wrapped
> > pattern to
> > > WSDL you require an element to have the same name as the
operation,
> > and
> > > you cannot have two elements with the same name in XML. So you
must
> > use
> > > the document/literal, non-wrapped style or one of the RPC styles
> > >
> > > Eg: non-wrapped style
> > > ----------------------
> > >
> > > ...
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > ...
> > >
> > > Currently I am working on this and implementing the support for
> > > non-wrapped style wsdl's.
> > >
> > > Regards,
> > > Amila Rathnayake.
> > >
> > >
> >
> >
>
> > ATTACHMENT part 2 application/octet-stream
name=GatewayWebService.wsdl
>
>
>
>
>
>
> __________________________________
> Do you Yahoo!?
> New and Improved Yahoo! Mail - 100MB free storage!
> http://promotions.yahoo.com/new_mail
_____
Do you Yahoo!?
Yahoo!
<http://us.rd.yahoo.com/mail_us/taglines/aac/*http:/promotions.yahoo.com
/new_mail/static/ease.html> Mail Address AutoComplete - You start. We
finish.
RE: Supporting for Non-Wrapped WSDL's
Posted by Amila Rathnayake <am...@opensource.lk>.
Hi,
Herewith I am sending another sample test project for testing the
support in non-wrapped style code generation for doc-lit wsdl's. Please
find the attached files with all the source and project files in
compressed format and the relevant simpleWS.wsdl file.
Please check this.
Thanks,
Amila.
-----Original Message-----
From: Samisa Abeysinghe [mailto:samisa_abeysinghe@yahoo.com]
Sent: Friday, August 06, 2004 10:24 PM
To: Apache AXIS C User List
Subject: RE: Supporting for Non-Wrapped WSDL's
Hi Amila,
Great stuff.
Thank you for the update.
Samisa...
Amila Rathnayake <am...@opensource.lk> wrote:
Hi Samisa,
I found one simple wsdl from the links given. Thank you for sending them
and I will be sending the VC++ sample test projects for this non-wrapped
support. The wsdl given in the other links are not that simple wsdl's
and therefore having lots of other complexities in them.
I've generated server and client for both simpleWS.wsdl and
GatewayWebService.wsdl that I have sent you earlier. The generated code
got compiled without any problems.
Thanks and Regards,
Amila Rathnayake.
> -----Original Message-----
> From: Samisa Abeysinghe [mailto:samisa_abeysinghe@yahoo.com]
> Sent: Thursday, August 05, 2004 4:15 PM
> To: Apache AXIS C User List; 'Apache AXIS C Developers List'
> Subject: RE: Supporting for Non-Wrapped WSDL's
>
> Hi Amila,
> Few places where I thik you can get the type of WSDLs you are
looking
> for.
> http://paracite.eprints.org/paracite.wsdl
> http://www.mail-archive.com/wsif-user@ws.apache.org/msg00420.html
> http://heasarc.gsfc.nasa.gov/itwg/wsdl_all.html
> http://www.freewebs.com/reude/simpleWS.wsdl
> http://www.mcdowall.com/wsdl/post-xmlstore.wsdl
> http://archives.us-vo.org/metadata/msg00378.html
> http://www.srdc.metu.edu.tr/~yavuz/MyAdmitVisit.wsdl
> http://www.srdc.metu.edu.tr/~yavuz/MyOrderEntry.wsdl
> http://www.intertwingly.net/stories/2002/03/05/weblogswsdl.html
> http://www.xmltoday.com/stock.wsdl
>
> Hope this helps.
> Thanks,
> Samisa...
>
>
>
> --- Amila Rathnayake wrote:
>
> > Hi All,
> >
> > Right now Axis C++ is supporting for wrapped style WSDL files.
> > Non-wrapped style WSDL 's are not supported and currently all the
> > doc-lit WSDL's are considered as wrapped style by default and
generating
> > the Skeletons and Stubs accordingly by the WSDL2WS tool.
> >
> > I have implemented the support for non-wrapped style wsdl. But for
> > testing purposes I need several valid WSDL's of non-wrapped style.
> >
> > I've found a simple WSDL which is in non-wrapped style. But that
WSDL is
> > having more than one part in the message. Then this should be an
invalid
> > wsdl since in the doc-lit type we can have only one part in the
message.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > I have attached the relevant WSDL file here with.
> >
> > If you have any idea, please comment on this.
> >
> > Btw if you have come across any non-wrapped style wsdl file, please
send
> > that file.
> >
> > Thanks and Regards,
> > Amila Rathnayake.
> >
> >
> >
> >
> > > -----Original Message-----
> > > From: amilar@opensource.lk [mailto:amilar@opensource.lk]
> > > Sent: Wednesday, July 21, 2004 6:31 PM
> > > To: Apache AXIS C Developers List
> > > Subject: Supporting for Non-Wrapped WSDL's
> > >
> > > Hi All,
> > >
> > > At this moment Axis is assuming and supporting only for Wrapped
style
> > > WSDL's.
> > >
> > > In wrapped style WSDL's, all method parameters are wrapped inside
an
> > > element named as the same name as operation and of the type of
> > > xsd:complextype.
> > >
> > > Ex: Wrapped Style
> > > -----------------
> > >
> > > ...
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > ...
> > >
> > > non-wrapped style
> > > =================
> > > But in Non-Wrapped style type is declared in the element tag.
> > > If you have overloaded operations, you cannot use the
document/literal
> > > wrapped style.
> > > WSDL allows overloaded operations. But when you add the wrapped
> > pattern to
> > > WSDL you require an element to have the same name as the
operation,
> > and
> > > you cannot have two elements with the same name in XML. So you
must
> > use
> > > the document/literal, non-wrapped style or one of the RPC styles
> > >
> > > Eg: non-wrapped style
> > > ----------------------
> > >
> > > ...
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > ...
> > >
> > > Currently I am working on this and implementing the support for
> > > non-wrapped style wsdl's.
> > >
> > > Regards,
> > > Amila Rathnayake.
> > >
> > >
> >
> >
>
> > ATTACHMENT part 2 application/octet-stream
name=GatewayWebService.wsdl
>
>
>
>
>
>
> __________________________________
> Do you Yahoo!?
> New and Improved Yahoo! Mail - 100MB free storage!
> http://promotions.yahoo.com/new_mail
_____
Do you Yahoo!?
Yahoo!
<http://us.rd.yahoo.com/mail_us/taglines/aac/*http:/promotions.yahoo.com
/new_mail/static/ease.html> Mail Address AutoComplete - You start. We
finish.
RE: Supporting for Non-Wrapped WSDL's
Posted by Samisa Abeysinghe <sa...@yahoo.com>.
Hi Amila,
Great stuff.
Thank you for the update.
Samisa...
Amila Rathnayake <am...@opensource.lk> wrote:
Hi Samisa,
I found one simple wsdl from the links given. Thank you for sending them
and I will be sending the VC++ sample test projects for this non-wrapped
support. The wsdl given in the other links are not that simple wsdl's
and therefore having lots of other complexities in them.
I've generated server and client for both simpleWS.wsdl and
GatewayWebService.wsdl that I have sent you earlier. The generated code
got compiled without any problems.
Thanks and Regards,
Amila Rathnayake.
> -----Original Message-----
> From: Samisa Abeysinghe [mailto:samisa_abeysinghe@yahoo.com]
> Sent: Thursday, August 05, 2004 4:15 PM
> To: Apache AXIS C User List; 'Apache AXIS C Developers List'
> Subject: RE: Supporting for Non-Wrapped WSDL's
>
> Hi Amila,
> Few places where I thik you can get the type of WSDLs you are
looking
> for.
> http://paracite.eprints.org/paracite.wsdl
> http://www.mail-archive.com/wsif-user@ws.apache.org/msg00420.html
> http://heasarc.gsfc.nasa.gov/itwg/wsdl_all.html
> http://www.freewebs.com/reude/simpleWS.wsdl
> http://www.mcdowall.com/wsdl/post-xmlstore.wsdl
> http://archives.us-vo.org/metadata/msg00378.html
> http://www.srdc.metu.edu.tr/~yavuz/MyAdmitVisit.wsdl
> http://www.srdc.metu.edu.tr/~yavuz/MyOrderEntry.wsdl
> http://www.intertwingly.net/stories/2002/03/05/weblogswsdl.html
> http://www.xmltoday.com/stock.wsdl
>
> Hope this helps.
> Thanks,
> Samisa...
>
>
>
> --- Amila Rathnayake wrote:
>
> > Hi All,
> >
> > Right now Axis C++ is supporting for wrapped style WSDL files.
> > Non-wrapped style WSDL 's are not supported and currently all the
> > doc-lit WSDL's are considered as wrapped style by default and
generating
> > the Skeletons and Stubs accordingly by the WSDL2WS tool.
> >
> > I have implemented the support for non-wrapped style wsdl. But for
> > testing purposes I need several valid WSDL's of non-wrapped style.
> >
> > I've found a simple WSDL which is in non-wrapped style. But that
WSDL is
> > having more than one part in the message. Then this should be an
invalid
> > wsdl since in the doc-lit type we can have only one part in the
message.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > I have attached the relevant WSDL file here with.
> >
> > If you have any idea, please comment on this.
> >
> > Btw if you have come across any non-wrapped style wsdl file, please
send
> > that file.
> >
> > Thanks and Regards,
> > Amila Rathnayake.
> >
> >
> >
> >
> > > -----Original Message-----
> > > From: amilar@opensource.lk [mailto:amilar@opensource.lk]
> > > Sent: Wednesday, July 21, 2004 6:31 PM
> > > To: Apache AXIS C Developers List
> > > Subject: Supporting for Non-Wrapped WSDL's
> > >
> > > Hi All,
> > >
> > > At this moment Axis is assuming and supporting only for Wrapped
style
> > > WSDL's.
> > >
> > > In wrapped style WSDL's, all method parameters are wrapped inside
an
> > > element named as the same name as operation and of the type of
> > > xsd:complextype.
> > >
> > > Ex: Wrapped Style
> > > -----------------
> > >
> > > ...
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > ...
> > >
> > > non-wrapped style
> > > =================
> > > But in Non-Wrapped style type is declared in the element tag.
> > > If you have overloaded operations, you cannot use the
document/literal
> > > wrapped style.
> > > WSDL allows overloaded operations. But when you add the wrapped
> > pattern to
> > > WSDL you require an element to have the same name as the
operation,
> > and
> > > you cannot have two elements with the same name in XML. So you
must
> > use
> > > the document/literal, non-wrapped style or one of the RPC styles
> > >
> > > Eg: non-wrapped style
> > > ----------------------
> > >
> > > ...
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > ...
> > >
> > > Currently I am working on this and implementing the support for
> > > non-wrapped style wsdl's.
> > >
> > > Regards,
> > > Amila Rathnayake.
> > >
> > >
> >
> >
>
> > ATTACHMENT part 2 application/octet-stream
name=GatewayWebService.wsdl
>
>
>
>
>
>
> __________________________________
> Do you Yahoo!?
> New and Improved Yahoo! Mail - 100MB free storage!
> http://promotions.yahoo.com/new_mail
---------------------------------
Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish.
RE: Supporting for Non-Wrapped WSDL's
Posted by Susantha Kumara <su...@opensource.lk>.
Hi Amila,
I looked at the wsdl and the generated code. If you run this code the
corresponding SOAP messages will lack the operation name (immediate
child element inside <Body> tag) . So the generated code should be as
follows,
The generated code in server side wrapper is
/* check whether we have got correct message */
if (AXIS_SUCCESS != pIWSDZ->checkMessageBody("in0",
"urn:webservice")) return AXIS_FAIL;
pIWSSZ->createSoapMethod("loadXMLDataReturn", "urn:webservice");
xsd__string v0 = pIWSDZ->getElementAsString("string",0);
if (AXIS_SUCCESS != (nStatus = pIWSDZ->getStatus())) return
nStatus;
try
{
xsd__string ret = pWs->loadXMLData(v0);
return pIWSSZ->addOutputParam("string", (void*)&ret,
XSD_STRING);
}
But IMO this should be,
/* check whether we have got correct message */
if (AXIS_SUCCESS != pIWSDZ->checkMessageBody("loadXMLData",
"urn:webservice")) return AXIS_FAIL;
pIWSSZ->createSoapMethod("loadXMLDataReturn", "urn:webservice");
xsd__string v0 = pIWSDZ->getElementAsString("in0",0);
if (AXIS_SUCCESS != (nStatus = pIWSDZ->getStatus())) return
nStatus;
try
{
xsd__string ret = pWs->loadXMLData(v0);
return pIWSSZ->addOutputParam("loadXMLDataReturn ", (void*)&ret,
XSD_STRING);
}
And
The generated code in client stub is
m_pCall->setOperation("in0", "urn:webservice");
applyUserPreferences();
m_pCall->addParameter((void*)&Value0, "string", XSD_STRING);
if (AXIS_SUCCESS == m_pCall->invoke())
{
if(AXIS_SUCCESS ==
m_pCall->checkMessage("loadXMLDataReturn", "urn:webservice"))
{
Ret = m_pCall->getElementAsString("string", 0);
}
}
But should be,
m_pCall->setOperation("loadXMLData", "urn:webservice");
applyUserPreferences();
m_pCall->addParameter((void*)&Value0, "in0", XSD_STRING);
if (AXIS_SUCCESS == m_pCall->invoke())
{
if(AXIS_SUCCESS ==
m_pCall->checkMessage("loadXMLDataReturn", "urn:webservice"))
{
Ret =
m_pCall->getElementAsString("loadXMLDataReturn", 0);
}
}
Susantha
---
> -----Original Message-----
> From: Amila Rathnayake [mailto:amilar@opensource.lk]
> Sent: Tuesday, August 10, 2004 5:26 PM
> To: 'Apache AXIS C Developers List'
> Subject: RE: Supporting for Non-Wrapped WSDL's
>
> Hi All,
>
> This is the second sample test for non-wrapped support. Attached file
> contains compressed source files and VC++ project files.
>
> Thanks,
> Amila.
>
> > -----Original Message-----
> > From: Amila Rathnayake [mailto:amilar@opensource.lk]
> > Sent: Monday, August 09, 2004 7:17 PM
> > To: axis-c-dev@ws.apache.org
> > Subject: RE: Supporting for Non-Wrapped WSDL's
> >
> >
> >
> > Hi,
> >
> > Here I am sending the implemented client and server sample
application
> > for testing the non-wrapped style code generation. I have attached
the
> > relevant wsdl file called GatewayWebService.wsdl as well.
> >
> > I have zipped all the source files for client and server and the
VC++
> > project files and also the *.dsw.
> >
> > Thanks and Regards,
> > Amila Rathnayake.
> >
> >
> >
> >
> > > -----Original Message-----
> > > From: Amila Rathnayake [mailto:amilar@opensource.lk]
> > > Sent: Friday, August 06, 2004 6:16 PM
> > > To: 'Apache AXIS C User List'
> > > Subject: RE: Supporting for Non-Wrapped WSDL's
> > >
> > >
> > >
> > > Hi Samisa,
> > >
> > > I found one simple wsdl from the links given. Thank you for
sending
> > them
> > > and I will be sending the VC++ sample test projects for this
> > non-wrapped
> > > support. The wsdl given in the other links are not that simple
> wsdl's
> > > and therefore having lots of other complexities in them.
> > >
> > > I've generated server and client for both simpleWS.wsdl and
> > > GatewayWebService.wsdl that I have sent you earlier. The generated
> > code
> > > got compiled without any problems.
> > >
> > > Thanks and Regards,
> > > Amila Rathnayake.
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: Samisa Abeysinghe [mailto:samisa_abeysinghe@yahoo.com]
> > > > Sent: Thursday, August 05, 2004 4:15 PM
> > > > To: Apache AXIS C User List; 'Apache AXIS C Developers List'
> > > > Subject: RE: Supporting for Non-Wrapped WSDL's
> > > >
> > > > Hi Amila,
> > > > Few places where I thik you can get the type of WSDLs you
are
> > > looking
> > > > for.
> > > > http://paracite.eprints.org/paracite.wsdl
> > > >
http://www.mail-archive.com/wsif-user@ws.apache.org/msg00420.html
> > > > http://heasarc.gsfc.nasa.gov/itwg/wsdl_all.html
> > > > http://www.freewebs.com/reude/simpleWS.wsdl
> > > > http://www.mcdowall.com/wsdl/post-xmlstore.wsdl
> > > > http://archives.us-vo.org/metadata/msg00378.html
> > > > http://www.srdc.metu.edu.tr/~yavuz/MyAdmitVisit.wsdl
> > > > http://www.srdc.metu.edu.tr/~yavuz/MyOrderEntry.wsdl
> > > > http://www.intertwingly.net/stories/2002/03/05/weblogswsdl.html
> > > > http://www.xmltoday.com/stock.wsdl
> > > >
> > > > Hope this helps.
> > > > Thanks,
> > > > Samisa...
> > > >
> > > >
> > > >
> > > > --- Amila Rathnayake <am...@opensource.lk> wrote:
> > > >
> > > > > Hi All,
> > > > >
> > > > > Right now Axis C++ is supporting for wrapped style WSDL files.
> > > > > Non-wrapped style WSDL 's are not supported and currently all
> the
> > > > > doc-lit WSDL's are considered as wrapped style by default and
> > > generating
> > > > > the Skeletons and Stubs accordingly by the WSDL2WS tool.
> > > > >
> > > > > I have implemented the support for non-wrapped style wsdl. But
> for
> > > > > testing purposes I need several valid WSDL's of non-wrapped
> style.
> > > > >
> > > > > I've found a simple WSDL which is in non-wrapped style. But
that
> > > WSDL is
> > > > > having more than one part in the message. Then this should be
an
> > > invalid
> > > > > wsdl since in the doc-lit type we can have only one part in
the
> > > message.
> > > > >
> > > > > <wsdl:message name="loadXMLDataRequest">
> > > > >
> > > > > <wsdl:part name="in0" element="impl:in0"/>
> > > > >
> > > > > <wsdl:part name="in1" element="impl:in1"/>
> > > > >
> > > > > </wsdl:message>
> > > > >
> > > > > I have attached the relevant WSDL file here with.
> > > > >
> > > > > If you have any idea, please comment on this.
> > > > >
> > > > > Btw if you have come across any non-wrapped style wsdl file,
> > please
> > > send
> > > > > that file.
> > > > >
> > > > > Thanks and Regards,
> > > > > Amila Rathnayake.
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: amilar@opensource.lk [mailto:amilar@opensource.lk]
> > > > > > Sent: Wednesday, July 21, 2004 6:31 PM
> > > > > > To: Apache AXIS C Developers List
> > > > > > Subject: Supporting for Non-Wrapped WSDL's
> > > > > >
> > > > > > Hi All,
> > > > > >
> > > > > > At this moment Axis is assuming and supporting only for
> Wrapped
> > > style
> > > > > > WSDL's.
> > > > > >
> > > > > > In wrapped style WSDL's, all method parameters are wrapped
> > inside
> > > an
> > > > > > element named as the same name as operation and of the type
of
> > > > > > xsd:complextype.
> > > > > >
> > > > > > Ex: Wrapped Style
> > > > > > -----------------
> > > > > >
> > > > > > ...
> > > > > > <types>
> > > > > > <xsd:schema targetNamespace="http://www.sample.org/" >
> > > > > > <xsd:element name="countWords">
> > > > > > <xsd:complexType>
> > > > > > <xsd:sequence>
> > > > > > <xsd:element name="words"
> type="xsd:string"
> > />
> > > > > > </xsd:sequence>
> > > > > > </xsd:complexType>
> > > > > > </xsd:element>
> > > > > > </xsd:schema>
> > > > > > </types>
> > > > > > <message name="countWordsInput">
> > > > > > <part name="iInputText" element="tns:countWords" />
> > > > > > </message>
> > > > > > ...
> > > > > >
> > > > > > non-wrapped style
> > > > > > =================
> > > > > > But in Non-Wrapped style type is declared in the element
tag.
> > > > > > If you have overloaded operations, you cannot use the
> > > document/literal
> > > > > > wrapped style.
> > > > > > WSDL allows overloaded operations. But when you add the
> wrapped
> > > > > pattern to
> > > > > > WSDL you require an element to have the same name as the
> > > operation,
> > > > > and
> > > > > > you cannot have two elements with the same name in XML. So
you
> > > must
> > > > > use
> > > > > > the document/literal, non-wrapped style or one of the RPC
> styles
> > > > > >
> > > > > > Eg: non-wrapped style
> > > > > > ----------------------
> > > > > >
> > > > > > ...
> > > > > > <types>
> > > > > > <xsd:schema targetNamespace="http://www.sample.org/" >
> > > > > > <xsd:element name="countWords" type="xsd:string" />
> > > > > > </xsd:schema>
> > > > > > </types>
> > > > > > <message name="countWordsInput">
> > > > > > <part name="iInputText" element="tns:countWords" />
> > > > > > </message>
> > > > > > ...
> > > > > >
> > > > > > Currently I am working on this and implementing the support
> for
> > > > > > non-wrapped style wsdl's.
> > > > > >
> > > > > > Regards,
> > > > > > Amila Rathnayake.
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > > > ATTACHMENT part 2 application/octet-stream
> > > name=GatewayWebService.wsdl
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > __________________________________
> > > > Do you Yahoo!?
> > > > New and Improved Yahoo! Mail - 100MB free storage!
> > > > http://promotions.yahoo.com/new_mail
RE: Supporting for Non-Wrapped WSDL's
Posted by Amila Rathnayake <am...@opensource.lk>.
Hi All,
This is the second sample test for non-wrapped support. Attached file
contains compressed source files and VC++ project files.
Thanks,
Amila.
> -----Original Message-----
> From: Amila Rathnayake [mailto:amilar@opensource.lk]
> Sent: Monday, August 09, 2004 7:17 PM
> To: axis-c-dev@ws.apache.org
> Subject: RE: Supporting for Non-Wrapped WSDL's
>
>
>
> Hi,
>
> Here I am sending the implemented client and server sample application
> for testing the non-wrapped style code generation. I have attached the
> relevant wsdl file called GatewayWebService.wsdl as well.
>
> I have zipped all the source files for client and server and the VC++
> project files and also the *.dsw.
>
> Thanks and Regards,
> Amila Rathnayake.
>
>
>
>
> > -----Original Message-----
> > From: Amila Rathnayake [mailto:amilar@opensource.lk]
> > Sent: Friday, August 06, 2004 6:16 PM
> > To: 'Apache AXIS C User List'
> > Subject: RE: Supporting for Non-Wrapped WSDL's
> >
> >
> >
> > Hi Samisa,
> >
> > I found one simple wsdl from the links given. Thank you for sending
> them
> > and I will be sending the VC++ sample test projects for this
> non-wrapped
> > support. The wsdl given in the other links are not that simple
wsdl's
> > and therefore having lots of other complexities in them.
> >
> > I've generated server and client for both simpleWS.wsdl and
> > GatewayWebService.wsdl that I have sent you earlier. The generated
> code
> > got compiled without any problems.
> >
> > Thanks and Regards,
> > Amila Rathnayake.
> >
> >
> >
> > > -----Original Message-----
> > > From: Samisa Abeysinghe [mailto:samisa_abeysinghe@yahoo.com]
> > > Sent: Thursday, August 05, 2004 4:15 PM
> > > To: Apache AXIS C User List; 'Apache AXIS C Developers List'
> > > Subject: RE: Supporting for Non-Wrapped WSDL's
> > >
> > > Hi Amila,
> > > Few places where I thik you can get the type of WSDLs you are
> > looking
> > > for.
> > > http://paracite.eprints.org/paracite.wsdl
> > > http://www.mail-archive.com/wsif-user@ws.apache.org/msg00420.html
> > > http://heasarc.gsfc.nasa.gov/itwg/wsdl_all.html
> > > http://www.freewebs.com/reude/simpleWS.wsdl
> > > http://www.mcdowall.com/wsdl/post-xmlstore.wsdl
> > > http://archives.us-vo.org/metadata/msg00378.html
> > > http://www.srdc.metu.edu.tr/~yavuz/MyAdmitVisit.wsdl
> > > http://www.srdc.metu.edu.tr/~yavuz/MyOrderEntry.wsdl
> > > http://www.intertwingly.net/stories/2002/03/05/weblogswsdl.html
> > > http://www.xmltoday.com/stock.wsdl
> > >
> > > Hope this helps.
> > > Thanks,
> > > Samisa...
> > >
> > >
> > >
> > > --- Amila Rathnayake <am...@opensource.lk> wrote:
> > >
> > > > Hi All,
> > > >
> > > > Right now Axis C++ is supporting for wrapped style WSDL files.
> > > > Non-wrapped style WSDL 's are not supported and currently all
the
> > > > doc-lit WSDL's are considered as wrapped style by default and
> > generating
> > > > the Skeletons and Stubs accordingly by the WSDL2WS tool.
> > > >
> > > > I have implemented the support for non-wrapped style wsdl. But
for
> > > > testing purposes I need several valid WSDL's of non-wrapped
style.
> > > >
> > > > I've found a simple WSDL which is in non-wrapped style. But that
> > WSDL is
> > > > having more than one part in the message. Then this should be an
> > invalid
> > > > wsdl since in the doc-lit type we can have only one part in the
> > message.
> > > >
> > > > <wsdl:message name="loadXMLDataRequest">
> > > >
> > > > <wsdl:part name="in0" element="impl:in0"/>
> > > >
> > > > <wsdl:part name="in1" element="impl:in1"/>
> > > >
> > > > </wsdl:message>
> > > >
> > > > I have attached the relevant WSDL file here with.
> > > >
> > > > If you have any idea, please comment on this.
> > > >
> > > > Btw if you have come across any non-wrapped style wsdl file,
> please
> > send
> > > > that file.
> > > >
> > > > Thanks and Regards,
> > > > Amila Rathnayake.
> > > >
> > > >
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: amilar@opensource.lk [mailto:amilar@opensource.lk]
> > > > > Sent: Wednesday, July 21, 2004 6:31 PM
> > > > > To: Apache AXIS C Developers List
> > > > > Subject: Supporting for Non-Wrapped WSDL's
> > > > >
> > > > > Hi All,
> > > > >
> > > > > At this moment Axis is assuming and supporting only for
Wrapped
> > style
> > > > > WSDL's.
> > > > >
> > > > > In wrapped style WSDL's, all method parameters are wrapped
> inside
> > an
> > > > > element named as the same name as operation and of the type of
> > > > > xsd:complextype.
> > > > >
> > > > > Ex: Wrapped Style
> > > > > -----------------
> > > > >
> > > > > ...
> > > > > <types>
> > > > > <xsd:schema targetNamespace="http://www.sample.org/" >
> > > > > <xsd:element name="countWords">
> > > > > <xsd:complexType>
> > > > > <xsd:sequence>
> > > > > <xsd:element name="words"
type="xsd:string"
> />
> > > > > </xsd:sequence>
> > > > > </xsd:complexType>
> > > > > </xsd:element>
> > > > > </xsd:schema>
> > > > > </types>
> > > > > <message name="countWordsInput">
> > > > > <part name="iInputText" element="tns:countWords" />
> > > > > </message>
> > > > > ...
> > > > >
> > > > > non-wrapped style
> > > > > =================
> > > > > But in Non-Wrapped style type is declared in the element tag.
> > > > > If you have overloaded operations, you cannot use the
> > document/literal
> > > > > wrapped style.
> > > > > WSDL allows overloaded operations. But when you add the
wrapped
> > > > pattern to
> > > > > WSDL you require an element to have the same name as the
> > operation,
> > > > and
> > > > > you cannot have two elements with the same name in XML. So you
> > must
> > > > use
> > > > > the document/literal, non-wrapped style or one of the RPC
styles
> > > > >
> > > > > Eg: non-wrapped style
> > > > > ----------------------
> > > > >
> > > > > ...
> > > > > <types>
> > > > > <xsd:schema targetNamespace="http://www.sample.org/" >
> > > > > <xsd:element name="countWords" type="xsd:string" />
> > > > > </xsd:schema>
> > > > > </types>
> > > > > <message name="countWordsInput">
> > > > > <part name="iInputText" element="tns:countWords" />
> > > > > </message>
> > > > > ...
> > > > >
> > > > > Currently I am working on this and implementing the support
for
> > > > > non-wrapped style wsdl's.
> > > > >
> > > > > Regards,
> > > > > Amila Rathnayake.
> > > > >
> > > > >
> > > >
> > > >
> > >
> > > > ATTACHMENT part 2 application/octet-stream
> > name=GatewayWebService.wsdl
> > >
> > >
> > >
> > >
> > >
> > >
> > > __________________________________
> > > Do you Yahoo!?
> > > New and Improved Yahoo! Mail - 100MB free storage!
> > > http://promotions.yahoo.com/new_mail
RE: Supporting for Non-Wrapped WSDL's
Posted by Amila Rathnayake <am...@opensource.lk>.
Hi,
Here I am sending the implemented client and server sample application
for testing the non-wrapped style code generation. I have attached the
relevant wsdl file called GatewayWebService.wsdl as well.
I have zipped all the source files for client and server and the VC++
project files and also the *.dsw.
Thanks and Regards,
Amila Rathnayake.
> -----Original Message-----
> From: Amila Rathnayake [mailto:amilar@opensource.lk]
> Sent: Friday, August 06, 2004 6:16 PM
> To: 'Apache AXIS C User List'
> Subject: RE: Supporting for Non-Wrapped WSDL's
>
>
>
> Hi Samisa,
>
> I found one simple wsdl from the links given. Thank you for sending
them
> and I will be sending the VC++ sample test projects for this
non-wrapped
> support. The wsdl given in the other links are not that simple wsdl's
> and therefore having lots of other complexities in them.
>
> I've generated server and client for both simpleWS.wsdl and
> GatewayWebService.wsdl that I have sent you earlier. The generated
code
> got compiled without any problems.
>
> Thanks and Regards,
> Amila Rathnayake.
>
>
>
> > -----Original Message-----
> > From: Samisa Abeysinghe [mailto:samisa_abeysinghe@yahoo.com]
> > Sent: Thursday, August 05, 2004 4:15 PM
> > To: Apache AXIS C User List; 'Apache AXIS C Developers List'
> > Subject: RE: Supporting for Non-Wrapped WSDL's
> >
> > Hi Amila,
> > Few places where I thik you can get the type of WSDLs you are
> looking
> > for.
> > http://paracite.eprints.org/paracite.wsdl
> > http://www.mail-archive.com/wsif-user@ws.apache.org/msg00420.html
> > http://heasarc.gsfc.nasa.gov/itwg/wsdl_all.html
> > http://www.freewebs.com/reude/simpleWS.wsdl
> > http://www.mcdowall.com/wsdl/post-xmlstore.wsdl
> > http://archives.us-vo.org/metadata/msg00378.html
> > http://www.srdc.metu.edu.tr/~yavuz/MyAdmitVisit.wsdl
> > http://www.srdc.metu.edu.tr/~yavuz/MyOrderEntry.wsdl
> > http://www.intertwingly.net/stories/2002/03/05/weblogswsdl.html
> > http://www.xmltoday.com/stock.wsdl
> >
> > Hope this helps.
> > Thanks,
> > Samisa...
> >
> >
> >
> > --- Amila Rathnayake <am...@opensource.lk> wrote:
> >
> > > Hi All,
> > >
> > > Right now Axis C++ is supporting for wrapped style WSDL files.
> > > Non-wrapped style WSDL 's are not supported and currently all the
> > > doc-lit WSDL's are considered as wrapped style by default and
> generating
> > > the Skeletons and Stubs accordingly by the WSDL2WS tool.
> > >
> > > I have implemented the support for non-wrapped style wsdl. But for
> > > testing purposes I need several valid WSDL's of non-wrapped style.
> > >
> > > I've found a simple WSDL which is in non-wrapped style. But that
> WSDL is
> > > having more than one part in the message. Then this should be an
> invalid
> > > wsdl since in the doc-lit type we can have only one part in the
> message.
> > >
> > > <wsdl:message name="loadXMLDataRequest">
> > >
> > > <wsdl:part name="in0" element="impl:in0"/>
> > >
> > > <wsdl:part name="in1" element="impl:in1"/>
> > >
> > > </wsdl:message>
> > >
> > > I have attached the relevant WSDL file here with.
> > >
> > > If you have any idea, please comment on this.
> > >
> > > Btw if you have come across any non-wrapped style wsdl file,
please
> send
> > > that file.
> > >
> > > Thanks and Regards,
> > > Amila Rathnayake.
> > >
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: amilar@opensource.lk [mailto:amilar@opensource.lk]
> > > > Sent: Wednesday, July 21, 2004 6:31 PM
> > > > To: Apache AXIS C Developers List
> > > > Subject: Supporting for Non-Wrapped WSDL's
> > > >
> > > > Hi All,
> > > >
> > > > At this moment Axis is assuming and supporting only for Wrapped
> style
> > > > WSDL's.
> > > >
> > > > In wrapped style WSDL's, all method parameters are wrapped
inside
> an
> > > > element named as the same name as operation and of the type of
> > > > xsd:complextype.
> > > >
> > > > Ex: Wrapped Style
> > > > -----------------
> > > >
> > > > ...
> > > > <types>
> > > > <xsd:schema targetNamespace="http://www.sample.org/" >
> > > > <xsd:element name="countWords">
> > > > <xsd:complexType>
> > > > <xsd:sequence>
> > > > <xsd:element name="words" type="xsd:string"
/>
> > > > </xsd:sequence>
> > > > </xsd:complexType>
> > > > </xsd:element>
> > > > </xsd:schema>
> > > > </types>
> > > > <message name="countWordsInput">
> > > > <part name="iInputText" element="tns:countWords" />
> > > > </message>
> > > > ...
> > > >
> > > > non-wrapped style
> > > > =================
> > > > But in Non-Wrapped style type is declared in the element tag.
> > > > If you have overloaded operations, you cannot use the
> document/literal
> > > > wrapped style.
> > > > WSDL allows overloaded operations. But when you add the wrapped
> > > pattern to
> > > > WSDL you require an element to have the same name as the
> operation,
> > > and
> > > > you cannot have two elements with the same name in XML. So you
> must
> > > use
> > > > the document/literal, non-wrapped style or one of the RPC styles
> > > >
> > > > Eg: non-wrapped style
> > > > ----------------------
> > > >
> > > > ...
> > > > <types>
> > > > <xsd:schema targetNamespace="http://www.sample.org/" >
> > > > <xsd:element name="countWords" type="xsd:string" />
> > > > </xsd:schema>
> > > > </types>
> > > > <message name="countWordsInput">
> > > > <part name="iInputText" element="tns:countWords" />
> > > > </message>
> > > > ...
> > > >
> > > > Currently I am working on this and implementing the support for
> > > > non-wrapped style wsdl's.
> > > >
> > > > Regards,
> > > > Amila Rathnayake.
> > > >
> > > >
> > >
> > >
> >
> > > ATTACHMENT part 2 application/octet-stream
> name=GatewayWebService.wsdl
> >
> >
> >
> >
> >
> >
> > __________________________________
> > Do you Yahoo!?
> > New and Improved Yahoo! Mail - 100MB free storage!
> > http://promotions.yahoo.com/new_mail
RE: Supporting for Non-Wrapped WSDL's
Posted by Amila Rathnayake <am...@opensource.lk>.
Hi Samisa,
I found one simple wsdl from the links given. Thank you for sending them
and I will be sending the VC++ sample test projects for this non-wrapped
support. The wsdl given in the other links are not that simple wsdl's
and therefore having lots of other complexities in them.
I've generated server and client for both simpleWS.wsdl and
GatewayWebService.wsdl that I have sent you earlier. The generated code
got compiled without any problems.
Thanks and Regards,
Amila Rathnayake.
> -----Original Message-----
> From: Samisa Abeysinghe [mailto:samisa_abeysinghe@yahoo.com]
> Sent: Thursday, August 05, 2004 4:15 PM
> To: Apache AXIS C User List; 'Apache AXIS C Developers List'
> Subject: RE: Supporting for Non-Wrapped WSDL's
>
> Hi Amila,
> Few places where I thik you can get the type of WSDLs you are
looking
> for.
> http://paracite.eprints.org/paracite.wsdl
> http://www.mail-archive.com/wsif-user@ws.apache.org/msg00420.html
> http://heasarc.gsfc.nasa.gov/itwg/wsdl_all.html
> http://www.freewebs.com/reude/simpleWS.wsdl
> http://www.mcdowall.com/wsdl/post-xmlstore.wsdl
> http://archives.us-vo.org/metadata/msg00378.html
> http://www.srdc.metu.edu.tr/~yavuz/MyAdmitVisit.wsdl
> http://www.srdc.metu.edu.tr/~yavuz/MyOrderEntry.wsdl
> http://www.intertwingly.net/stories/2002/03/05/weblogswsdl.html
> http://www.xmltoday.com/stock.wsdl
>
> Hope this helps.
> Thanks,
> Samisa...
>
>
>
> --- Amila Rathnayake <am...@opensource.lk> wrote:
>
> > Hi All,
> >
> > Right now Axis C++ is supporting for wrapped style WSDL files.
> > Non-wrapped style WSDL 's are not supported and currently all the
> > doc-lit WSDL's are considered as wrapped style by default and
generating
> > the Skeletons and Stubs accordingly by the WSDL2WS tool.
> >
> > I have implemented the support for non-wrapped style wsdl. But for
> > testing purposes I need several valid WSDL's of non-wrapped style.
> >
> > I've found a simple WSDL which is in non-wrapped style. But that
WSDL is
> > having more than one part in the message. Then this should be an
invalid
> > wsdl since in the doc-lit type we can have only one part in the
message.
> >
> > <wsdl:message name="loadXMLDataRequest">
> >
> > <wsdl:part name="in0" element="impl:in0"/>
> >
> > <wsdl:part name="in1" element="impl:in1"/>
> >
> > </wsdl:message>
> >
> > I have attached the relevant WSDL file here with.
> >
> > If you have any idea, please comment on this.
> >
> > Btw if you have come across any non-wrapped style wsdl file, please
send
> > that file.
> >
> > Thanks and Regards,
> > Amila Rathnayake.
> >
> >
> >
> >
> > > -----Original Message-----
> > > From: amilar@opensource.lk [mailto:amilar@opensource.lk]
> > > Sent: Wednesday, July 21, 2004 6:31 PM
> > > To: Apache AXIS C Developers List
> > > Subject: Supporting for Non-Wrapped WSDL's
> > >
> > > Hi All,
> > >
> > > At this moment Axis is assuming and supporting only for Wrapped
style
> > > WSDL's.
> > >
> > > In wrapped style WSDL's, all method parameters are wrapped inside
an
> > > element named as the same name as operation and of the type of
> > > xsd:complextype.
> > >
> > > Ex: Wrapped Style
> > > -----------------
> > >
> > > ...
> > > <types>
> > > <xsd:schema targetNamespace="http://www.sample.org/" >
> > > <xsd:element name="countWords">
> > > <xsd:complexType>
> > > <xsd:sequence>
> > > <xsd:element name="words" type="xsd:string" />
> > > </xsd:sequence>
> > > </xsd:complexType>
> > > </xsd:element>
> > > </xsd:schema>
> > > </types>
> > > <message name="countWordsInput">
> > > <part name="iInputText" element="tns:countWords" />
> > > </message>
> > > ...
> > >
> > > non-wrapped style
> > > =================
> > > But in Non-Wrapped style type is declared in the element tag.
> > > If you have overloaded operations, you cannot use the
document/literal
> > > wrapped style.
> > > WSDL allows overloaded operations. But when you add the wrapped
> > pattern to
> > > WSDL you require an element to have the same name as the
operation,
> > and
> > > you cannot have two elements with the same name in XML. So you
must
> > use
> > > the document/literal, non-wrapped style or one of the RPC styles
> > >
> > > Eg: non-wrapped style
> > > ----------------------
> > >
> > > ...
> > > <types>
> > > <xsd:schema targetNamespace="http://www.sample.org/" >
> > > <xsd:element name="countWords" type="xsd:string" />
> > > </xsd:schema>
> > > </types>
> > > <message name="countWordsInput">
> > > <part name="iInputText" element="tns:countWords" />
> > > </message>
> > > ...
> > >
> > > Currently I am working on this and implementing the support for
> > > non-wrapped style wsdl's.
> > >
> > > Regards,
> > > Amila Rathnayake.
> > >
> > >
> >
> >
>
> > ATTACHMENT part 2 application/octet-stream
name=GatewayWebService.wsdl
>
>
>
>
>
>
> __________________________________
> Do you Yahoo!?
> New and Improved Yahoo! Mail - 100MB free storage!
> http://promotions.yahoo.com/new_mail
RE: Supporting for Non-Wrapped WSDL's
Posted by Samisa Abeysinghe <sa...@yahoo.com>.
Hi Amila,
Few places where I thik you can get the type of WSDLs you are looking for.
http://paracite.eprints.org/paracite.wsdl
http://www.mail-archive.com/wsif-user@ws.apache.org/msg00420.html
http://heasarc.gsfc.nasa.gov/itwg/wsdl_all.html
http://www.freewebs.com/reude/simpleWS.wsdl
http://www.mcdowall.com/wsdl/post-xmlstore.wsdl
http://archives.us-vo.org/metadata/msg00378.html
http://www.srdc.metu.edu.tr/~yavuz/MyAdmitVisit.wsdl
http://www.srdc.metu.edu.tr/~yavuz/MyOrderEntry.wsdl
http://www.intertwingly.net/stories/2002/03/05/weblogswsdl.html
http://www.xmltoday.com/stock.wsdl
Hope this helps.
Thanks,
Samisa...
--- Amila Rathnayake <am...@opensource.lk> wrote:
> Hi All,
>
> Right now Axis C++ is supporting for wrapped style WSDL files.
> Non-wrapped style WSDL 's are not supported and currently all the
> doc-lit WSDL's are considered as wrapped style by default and generating
> the Skeletons and Stubs accordingly by the WSDL2WS tool.
>
> I have implemented the support for non-wrapped style wsdl. But for
> testing purposes I need several valid WSDL's of non-wrapped style.
>
> I've found a simple WSDL which is in non-wrapped style. But that WSDL is
> having more than one part in the message. Then this should be an invalid
> wsdl since in the doc-lit type we can have only one part in the message.
>
> <wsdl:message name="loadXMLDataRequest">
>
> <wsdl:part name="in0" element="impl:in0"/>
>
> <wsdl:part name="in1" element="impl:in1"/>
>
> </wsdl:message>
>
> I have attached the relevant WSDL file here with.
>
> If you have any idea, please comment on this.
>
> Btw if you have come across any non-wrapped style wsdl file, please send
> that file.
>
> Thanks and Regards,
> Amila Rathnayake.
>
>
>
>
> > -----Original Message-----
> > From: amilar@opensource.lk [mailto:amilar@opensource.lk]
> > Sent: Wednesday, July 21, 2004 6:31 PM
> > To: Apache AXIS C Developers List
> > Subject: Supporting for Non-Wrapped WSDL's
> >
> > Hi All,
> >
> > At this moment Axis is assuming and supporting only for Wrapped style
> > WSDL's.
> >
> > In wrapped style WSDL's, all method parameters are wrapped inside an
> > element named as the same name as operation and of the type of
> > xsd:complextype.
> >
> > Ex: Wrapped Style
> > -----------------
> >
> > ...
> > <types>
> > <xsd:schema targetNamespace="http://www.sample.org/" >
> > <xsd:element name="countWords">
> > <xsd:complexType>
> > <xsd:sequence>
> > <xsd:element name="words" type="xsd:string" />
> > </xsd:sequence>
> > </xsd:complexType>
> > </xsd:element>
> > </xsd:schema>
> > </types>
> > <message name="countWordsInput">
> > <part name="iInputText" element="tns:countWords" />
> > </message>
> > ...
> >
> > non-wrapped style
> > =================
> > But in Non-Wrapped style type is declared in the element tag.
> > If you have overloaded operations, you cannot use the document/literal
> > wrapped style.
> > WSDL allows overloaded operations. But when you add the wrapped
> pattern to
> > WSDL you require an element to have the same name as the operation,
> and
> > you cannot have two elements with the same name in XML. So you must
> use
> > the document/literal, non-wrapped style or one of the RPC styles
> >
> > Eg: non-wrapped style
> > ----------------------
> >
> > ...
> > <types>
> > <xsd:schema targetNamespace="http://www.sample.org/" >
> > <xsd:element name="countWords" type="xsd:string" />
> > </xsd:schema>
> > </types>
> > <message name="countWordsInput">
> > <part name="iInputText" element="tns:countWords" />
> > </message>
> > ...
> >
> > Currently I am working on this and implementing the support for
> > non-wrapped style wsdl's.
> >
> > Regards,
> > Amila Rathnayake.
> >
> >
>
>
> ATTACHMENT part 2 application/octet-stream name=GatewayWebService.wsdl
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
http://promotions.yahoo.com/new_mail
RE: Supporting for Non-Wrapped WSDL's
Posted by Samisa Abeysinghe <sa...@yahoo.com>.
Hi Amila,
Few places where I thik you can get the type of WSDLs you are looking for.
http://paracite.eprints.org/paracite.wsdl
http://www.mail-archive.com/wsif-user@ws.apache.org/msg00420.html
http://heasarc.gsfc.nasa.gov/itwg/wsdl_all.html
http://www.freewebs.com/reude/simpleWS.wsdl
http://www.mcdowall.com/wsdl/post-xmlstore.wsdl
http://archives.us-vo.org/metadata/msg00378.html
http://www.srdc.metu.edu.tr/~yavuz/MyAdmitVisit.wsdl
http://www.srdc.metu.edu.tr/~yavuz/MyOrderEntry.wsdl
http://www.intertwingly.net/stories/2002/03/05/weblogswsdl.html
http://www.xmltoday.com/stock.wsdl
Hope this helps.
Thanks,
Samisa...
--- Amila Rathnayake <am...@opensource.lk> wrote:
> Hi All,
>
> Right now Axis C++ is supporting for wrapped style WSDL files.
> Non-wrapped style WSDL 's are not supported and currently all the
> doc-lit WSDL's are considered as wrapped style by default and generating
> the Skeletons and Stubs accordingly by the WSDL2WS tool.
>
> I have implemented the support for non-wrapped style wsdl. But for
> testing purposes I need several valid WSDL's of non-wrapped style.
>
> I've found a simple WSDL which is in non-wrapped style. But that WSDL is
> having more than one part in the message. Then this should be an invalid
> wsdl since in the doc-lit type we can have only one part in the message.
>
> <wsdl:message name="loadXMLDataRequest">
>
> <wsdl:part name="in0" element="impl:in0"/>
>
> <wsdl:part name="in1" element="impl:in1"/>
>
> </wsdl:message>
>
> I have attached the relevant WSDL file here with.
>
> If you have any idea, please comment on this.
>
> Btw if you have come across any non-wrapped style wsdl file, please send
> that file.
>
> Thanks and Regards,
> Amila Rathnayake.
>
>
>
>
> > -----Original Message-----
> > From: amilar@opensource.lk [mailto:amilar@opensource.lk]
> > Sent: Wednesday, July 21, 2004 6:31 PM
> > To: Apache AXIS C Developers List
> > Subject: Supporting for Non-Wrapped WSDL's
> >
> > Hi All,
> >
> > At this moment Axis is assuming and supporting only for Wrapped style
> > WSDL's.
> >
> > In wrapped style WSDL's, all method parameters are wrapped inside an
> > element named as the same name as operation and of the type of
> > xsd:complextype.
> >
> > Ex: Wrapped Style
> > -----------------
> >
> > ...
> > <types>
> > <xsd:schema targetNamespace="http://www.sample.org/" >
> > <xsd:element name="countWords">
> > <xsd:complexType>
> > <xsd:sequence>
> > <xsd:element name="words" type="xsd:string" />
> > </xsd:sequence>
> > </xsd:complexType>
> > </xsd:element>
> > </xsd:schema>
> > </types>
> > <message name="countWordsInput">
> > <part name="iInputText" element="tns:countWords" />
> > </message>
> > ...
> >
> > non-wrapped style
> > =================
> > But in Non-Wrapped style type is declared in the element tag.
> > If you have overloaded operations, you cannot use the document/literal
> > wrapped style.
> > WSDL allows overloaded operations. But when you add the wrapped
> pattern to
> > WSDL you require an element to have the same name as the operation,
> and
> > you cannot have two elements with the same name in XML. So you must
> use
> > the document/literal, non-wrapped style or one of the RPC styles
> >
> > Eg: non-wrapped style
> > ----------------------
> >
> > ...
> > <types>
> > <xsd:schema targetNamespace="http://www.sample.org/" >
> > <xsd:element name="countWords" type="xsd:string" />
> > </xsd:schema>
> > </types>
> > <message name="countWordsInput">
> > <part name="iInputText" element="tns:countWords" />
> > </message>
> > ...
> >
> > Currently I am working on this and implementing the support for
> > non-wrapped style wsdl's.
> >
> > Regards,
> > Amila Rathnayake.
> >
> >
>
>
> ATTACHMENT part 2 application/octet-stream name=GatewayWebService.wsdl
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
http://promotions.yahoo.com/new_mail