So in axis2 it is enough to change it in the wsdl file? Axis2 does automaticaly parse the input?
> -----Ursprüngliche Nachricht----- > Von: [email protected] > Gesendet: 22.03.06 01:57:17 > An: [email protected] > Betreff: Re: differences between axis and axis2 (styles and lit vs enc) In Axis 1, you can specify your style/use in three ways: > > 1. in the WSDL description (see Robert's example) > 2. in the WSDD: > > <service name="<name> provider="<provider>" > style="rpc|wrapped|document|message" > use="encoded|literal">3. in java2wsdl: > > -y, --style <argument> > The style of binding in the WSDL, either DOCUMENT, RPC, or WRAPPED. > > -u, --use <argument> > The use of items in the binding, either LITERAL or ENCODEDThe default is > rpc/encoded. > > Anne > > > On 3/21/06, > robert lazarski <[EMAIL PROTECTED]> wrote: > > You can't have, AFAIK, doc / lit etc without a wsdl. I personally look > at a wsdl in four parts. The last part, as I see it, you define the > style: > > <binding name="LoginEndpointBinding" type="tns:LoginEndpoint"> > <soap:binding transport=" > http://schemas.xmlsoap.org/soap/http > " style="document"/> > <operation name="webLogin"> > <soap:operation soapAction="webLogin"/> > <input name="LoginEndpoint_webLogin"> > <soap:body use="literal"/> > > </input> > <output name="LoginEndpoint_webLoginResponse"> > <soap:body use="literal"/> > </output> > > > </operation> > </binding> > > Notice style="document" and use="literal" . Of course you need to follow the > conventions in the ibm article. > Not sure how to do what you describe in axis 1.x . > > > HTH, > Robert > http://www.braziloutsource.com > > > > > On 3/21/06, SOA Work <[EMAIL PROTECTED]> wrote: > > > Not exactly. Maybe I get you wrong. > > I > read the wsdl paper from ibm (thats the reason why I am intrested in > the different styles). I would like to know if I can use axis2 with the > different styles and how I configure which one to use? > > My second > question is about axis not axis2. I would like to know if I can create > a document-centric service with axis. I don't want the message to be > mapped to java beans or something. I would like to have a dom tree (or > something similar) in my service class method. axis2 has the > possibility to get an OMElement Object f.e. > > > > > -----Ursprüngliche Nachricht----- > > Von: > [email protected] > > Gesendet: 21.03.06 14:20:33 > > An: [email protected] > > Betreff: Re: differences between axis and axis2 (styles and lit vs enc) > > Roughly speaking doc/lit and rpc/lit are databinding styles that allow > > > for complex objects, ie, customized classes with getters and setters, > > to be defined via WSDL. The differences in these styles and how to > > define them are explained pretty well here: > > > > http://www-128.ibm.com/developerworks/webservices/library/ws-whichwsdl/ > > > > > You can transform the wsdl to Java sources via wsdl2java and such. > > > wsdl2java in Axis2 internally has options for either xmlbeans, adb, > > jaxme or perhaps someday jaxb. > > > > Now if you've used jaxb or xmlbeans in pure java, or read the many docs > > explaining what they do, then you'll then have a good start knowing how > > > to "create a service with axis which receives some sort of xml tree > > inside the java methods" . > > > > Does that answer your question? > > > > HTH, > > Robert > > > http://www.braziloutsource.com/ > > > > > > On 3/21/06, SOA Work <[EMAIL PROTECTED]> wrote: > > > > thx. > > rpc/enc should also be avoided (ws-i). > > > > > how can I configure the use of doc/lit <-> rpc/lit? > > > > > Does somebody know if there's a way to create a service with axis which > receives some sort of xml tree inside the java methods? > > > > > > Dominik > > > > > > > -----Ursprüngliche Nachricht----- > > > Von: > [email protected] > > > > Gesendet: 21.03.06 06:16:28 > > > An: > > [email protected] > > > Betreff: Re: differences between axis and axis2 (styles and lit vs enc) > > > > > doc/enc is not supported (and doesn't make any sense -- it's not a valid > > combination). > > > wrapped = doc/lit using a specific convention. It isn't a separate > > > style/use combination. > > > > > > > > > Axis2 currently supports doc/lit and rpc/lit. > > > > > > > > > Anne > > > > > > > > > On 3/20/06, SOA Work < > [EMAIL PROTECTED]> wrote: > > > > > > > Hi, > > > > > > > > I'm looking for the differences between axis and axis2. > > > At the moment I'm trying to find out which styles and encodings are > > > supported. > > > > > > > > > (with document-centric I mean the possibility to get the message as xml > > tree. in axis2 this is covered via RawXMLMessageReceiver and OMElement) > > > > > > > > > axis: > > > rpc/enc > > > rpc/lit > > > doc/enc > > > doc/lit > > > wrapped > > > --------------------> all supported > > > > > no way to create a message-centric web service > > > > > > > > > > axis2: > > > rpc/enc (<- I read it should be supported) > > > > > > rpc/lit > > > what about the others? > > > > > > easy message-centric services (RawXMLMessageReceiver) > > > > > > > > > > > > And how to I configure the style and the use (<- encoded vs literal) > > > > > > thx > > > Dominik > > > ______________________________________________________________ > > > > > > > Verschicken Sie romantische, coole und witzige Bilder per SMS! > > > > > Jetzt bei WEB.DE > FreeMail: http://f.web.de/?mc=021193 > > > > > > > > > > > > > > > > ______________________________________________________________________ > > > > XXL-Speicher, PC-Virenschutz, Spartarife & mehr: Nur im > WEB.DE Club! > > Jetzt gratis testen! http://freemail.web.de/home/landingpad/?mc=021130 > > > > > > > > > > > > ______________________________________________________________ > > Verschicken Sie romantische, coole und witzige Bilder per SMS! > Jetzt bei WEB.DE FreeMail: > http://f.web.de/?mc=021193 > > > > ______________________________________________________________________ XXL-Speicher, PC-Virenschutz, Spartarife & mehr: Nur im WEB.DE Club! Jetzt gratis testen! http://freemail.web.de/home/landingpad/?mc=021130
