axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anne Thomas Manes" <atma...@gmail.com>
Subject Re: WSDD to set up an RPC/Literal service
Date Fri, 21 Apr 2006 16:19:38 GMT
.NET doesn't support RPC/Literal (although Indigo will). For best
interoperability with .NET, you want to use "wrapped" document/literal.
(From a programming perspective, WRAPPED is pretty much identical to RPC
style).

In java2wsdl, specify -yWRAPPED.
In WSDD, specify style="WRAPPED".

Anne

On 4/21/06, Kevin O'Rourke <kevin@caboose.org.uk> wrote:
>
> I was trying to do RPC/literal rather than Document/literal.
>
> Does this mean that I have to start with the WSDL and generate server
> stub classes from it if I want to do anything other than the default
> RPC/encoded?
>
> Kevin
>
> James Clinton wrote:
> > You define the service as Doc/Lit in the WSDL binding.
> >
> > Here is a snippet example...
> >
> >       <wsdl:binding name="X" type="intf:X">
> >               <wsdlsoap:binding style="document"
> > transport="http://schemas.xmlsoap.org/soap/http" />  <!-- defined as
> > document -->
> >
> >               <wsdl:operation name="doX">
> >                       <wsdlsoap:operation soapAction="" />
> >                       <wsdl:input>
> >                               <wsdlsoap:body use="literal" />   <!--
> > input defined as literial -->
> >                       </wsdl:input>
> >                       <wsdl:output>
> >                               <wsdlsoap:body use="literal" />
> >                       </wsdl:output>
> >                       <wsdl:fault name="XyzException">
> >                               <wsdlsoap:fault use="literal" />
> >                       </wsdl:fault>
> >                       </wsdl:operation>
> >
> >
> > HTH, James.
> >
> > -----Original Message-----
> > From: Kevin O'Rourke [mailto:kevin@caboose.org.uk]
> > Sent: 21 April 2006 16:20
> > To: axis-user@ws.apache.org
> > Subject: WSDD to set up an RPC/Literal service
> >
> >
> > Hi,
> >
> > I'm writing a web service with Axis and am starting to get somewhere.
> >
> > The service will have to interoperate with .Net (specifically VB.Net),
> > so I want to stick to WS-I Basic, which means I can't use RPC/Encoded.
> > In fact some of the Microsoft tools complain if they come across any
> > 'use="encoded"' attributes in the WSDL.
> >
> > Axis (1.3) seems to default to creating an RPC/Encoded service if I
> > deploy a Java class.  Is there some way to tell it to use RPC/Literal
> > instead?  I'm thinking that the WSDD file would be the place to look,
> > but I can't find anything relevant in the docs.
> >
> > Thanks,
> > Kevin
> >
> >
> >
> > -----------------------------------------------------
> > THE INFORMATION IN THIS E-MAIL AND IN ANY ATTACHMENTS IS CONFIDENTIAL
> >
> > AND MAY BE PRIVILEGED OR OTHERWISE PROTECTED FROM DISCLOSURE.
> > IF YOU ARE NOT THE INTENDED RECIPIENT AND HAVE RECEIVED IT IN ERROR YOU
> ARE ON NOTICE OF ITS STATUS.
> > PLEASE NOTIFY THE SENDER IMMEDIATELY BY RETURN EMAIL AND THEN DELETE
> THIS EMAIL AND ANY ATTACHMENT FROM YOUR SYSTEM.
> > YOU MUST NOT RETAIN, COPY OR USE THIS E-MAIL OR ANY ATTACHMENT FOR ANY
> PURPOSE, NOR DISCLOSE ALL OR ANY PART OF ITS CONTENTS TO ANY OTHER PERSON:
> >
> > TO DO SO COULD BE A BREACH OF CONFIDENCE
> >
> > EMAIL MAY BE SUSCEPTIBLE TO DATA CORRUPTION, INTERCEPTION AND
> UNAUTHORISED AMENDMENT,
> > AND WE DO NOT ACCEPT LIABILITY FOR ANY SUCH CORRUPTION, INTERCEPTION OR
> AMENDMENT OR THE CONSEQUENCES THEREOF.
> >
> > WE MAY MONITOR THE CONTENT OF EMAILS SENT AND RECEIVED VIA OUR NETWORK
> FOR VIRUSES OR UNAUTHORISED USE AND FOR OTHER LAWFUL BUSINESS PURPOSES.
> > WE DO NOT ACCEPT RESPONSIBILITY FOR ANY LOSS OR DAMAGE ARISING FROM A
> VIRUS IN ANY EMAIL OR ATTACHMENT.
> >
> > -----------------------------------------------
> > postmaster@ins-sure.com
> >
> >
> >
> >
>
>

Mime
View raw message