Because that's how Axis2 works .. the generated classes are the ones who
serialize / deser themselves into the elements that flow.
Sanjiva.
Karuppusamy, Thamayanthi (Consultant) wrote:
My question is why it is generating different class for request and
response element.
part
<types>
<types>
<xsd:schema ...........>
<xsd:element name="requestXML" type="xsd:string"/>
<xsd:element name="executeReturn" type="xsd:string"/>
</xsd:schema>
</types>
<message name="executeRequest">
<part name="requestXML" element="ui2s:requestXML"/>
</message>
<message name="executeResponse">
<part name="executeReturn" element="ui2s:executeReturn"/>
</message>
<portType name="UI2SServicePortType">
<operation name="execute">
<input message="ui2s:executeRequest"/>
<output message="ui2s:executeResponse"/>
</operation>
</portType>
<xsd:element name="requestXML" type="xsd:string"/>
<xsd:element name="executeReturn" type="xsd:string"/>
</xsd:schema>
</types>
<message name="executeRequest">
<part name="requestXML" element="ui2s:requestXML"/>
</message>
<message name="executeResponse">
<part name="executeReturn" element="ui2s:executeReturn"/>
</message>
<portType name="UI2SServicePortType">
<operation name="execute">
<input message="ui2s:executeRequest"/>
<output message="ui2s:executeResponse"/>
</operation>
</portType>
Thanks & Regards
Thamayanthi Karuppusamy
------------------------------------------------------------------------
*From:* Amila Suriarachchi [mailto:[EMAIL PROTECTED]
*Sent:* Wednesday, August 22, 2007 10:51 AM
*To:* [email protected]
*Subject:* Re: AXIS2 Skeleton and Stub Generation
On 8/21/07, *Anne Thomas Manes* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
Axis2 support of RPC/literal is sketchy at best, considering that you
must edit the WSDL to tell Axis2 how to handle it.
See http://ws.apache.org/axis2/1_3/Axis2-rpc-support.html
<http://ws.apache.org/axis2/1_3/Axis2-rpc-support.html>
thanks Anne to pointing out this document. this seems to be an
obsolete documnet.
according to the basic profile we can not have elements in parts for rpc
literal. earlier it generated an element reference and now it has fixed.
It is true that at wsdl11ToAxisService builder an rpc stlye document is
converted to the document/literal type. but it is done totally according
to the rules with wsdl spec and basic profile. Hence message processing
is done accordingly. And displaying the wsdl with the ?wsdl it displays
the correct original wsdl as well.
And axis2 supports parameters like parameterOrder, parts as well.
thanks,
Amila.
Anne
On 8/20/07, Amila Suriarachchi <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
>
>
> On 8/19/07, Anne Thomas Manes < [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
> > Use of types in a message part (rather than an element)
indicates that
> > you are using an RPC style service. You should be using
document style
> > with Axis2.
>
> Axis2 supports RPC style. but only literal. so if you wsdl is
rpc/literal
> then you can use Axis2.
> but Axis2 does not support rpc/encoded.
>
> >
> > Anne
> >
> > On 8/19/07, Karuppusamy, Thamayanthi (Consultant)
> > <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
> > >
> > >
> > > Hi,
> > >
> > > How the stub and skeleton class are generated in AXIS2?.
because It is
> > > totally different from AXIS 1.3 . For Example
> > > <wsdl:message name="executeResponse">
> > >
> > >
> > > <wsdl:part name="executeReturn" type="xsd:string"/>
> > >
> > > </wsdl:message>
> > > above is created as one class Execute and ExecuteResponse
etc., why it
> is
> > > creating like, but previous version is not creating like this.
> > >
> > > What is use of ExtensionMapper and *
MessageReceiverInOut.java file, I
> have
> > > searched the *MessageReceiverInOut no where used this file in
skeleton
> or
> > > other files
> > >
> > > Can anyone please help me?
> > >
> > >
> > > Thanks & Regards
> > > Thamayanthi Karuppusamy
> > >
> > >
> > >
> > > ________________________________
> > >
> > >
> > >
> > >
> > > This email may contain confidential and privileged material
for the
> sole
> > > use of the intended recipient(s). Any review, use, retention,
> distribution
> > > or disclosure by others is strictly prohibited. If you are
not the
> intended
> > > recipient (or authorized to receive for the recipient),
please contact
> the
> > > sender by reply email and delete all copies of this message.
Also, email
> is
> > > susceptible to data corruption, interception, tampering,
unauthorized
> > > amendment and viruses. We only send and receive emails on the
basis that
> we
> > > are not liable for any such corruption, interception, tampering,
> amendment
> > > or viruses or any consequence thereof.
> >
> >
>
---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
> > For additional commands, e-mail: [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
> >
> >
>
>
>
> --
> Amila Suriarachchi,
> WSO2 Inc.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
--
Amila Suriarachchi,
WSO2 Inc.
--
Sanjiva Weerawarana, Ph.D.
Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
Member; Apache Software Foundation; http://www.apache.org/
Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
