Re: some axis2 deployment questions
Hi Dominik please see my in line comments. SOA Work wrote: >Hi, > >I'm going to publish a simple service using axis2 war distribution. >Now I'm running into some (maybe simple) questions, which I can not solve with >the user guide: > >1) what's the difference between RawXML and RPC message receivers? >With RawXML the methods signature gets OMElement input and output? If I don't >want to change my business class I have to use RPCMessageReceiver, right? > > RPCMessageReciver does not mean RPC style in WSDL , it is just Java reflection based message receiver and which can handler simple types , and array of them , ArratList and OMElemnts. RawXML is just to handle OM in OM out case. Yes if you are not going to your business class then you have to use RPCMessage receiver or you have to write your own message receiver. >2) can I use patterns like: "*" or multiple operations names like "getString >getInt" to publish a bunch of operations? > > > In the current impl if you dont specify any of the operation in services.xml then all the public method will be published , but soon there will be way to exclude some of them. >3) If I don't specify any operation inside my element all operations >are published. Can I set the messageReceiver to use for all operations? > > > yes you can , and you can do that by adding following entry in services.xml http://www.w3.org/2004/08/wsdl/in-only"; class="org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver"/> http://www.w3.org/2004/08/wsdl/in-out"; class="org.apache.axis2.rpc.receivers.RPCMessageReceiver"/> >4) My resulting wsdl file is literal but I want ther rpc encoded style. How >can I change this? > > hmmm , the wsdl you are getting is auto generated one , and we only generate doc-lit wsdl , if you want to use rpc you have to write your own rpc wsdl and put that into META-INF directory of the service aar. >thx a lot >Dominik >__ >Verschicken Sie romantische, coole und witzige Bilder per SMS! >Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193 > > > > > -- Thanks, Deepal ~Future is Open~
Re: some axis2 deployment questions
rpc literal is a wsdl style. From what you stated you don't seem to be using wsdl. Check out the latest source for the file: xdocs/latest/resources/schemas/services.xsd I recommend reading the article "avoiding mistakes made using axis2" : http://www.developer.com/open/article.php/10930_3589126_1 HTH, Robert http://www.braziloutsource.comOn 3/15/06, SOA Work <[EMAIL PROTECTED] > wrote:Ok. How and where can I configure the style (rpc/literal f.e)? Sorry I made a mistake. I called the messageReceiver Handler.-> My question: Can I define a messageReceiver for all operations? If I want 20 operations to use the RPCMessageReceiver do I need 20 entries in my service element?ThxDominikp.s.: Is there any dtd or xls file around for the service.xml? This would answer all my questions instantly ;-)> -Ursprüngliche Nachricht-> Von: axis-user@ws.apache.org> Gesendet: 15.03.06 14:51:21> An: axis-user@ws.apache.org> Betreff: Re: some axis2 deployment questions You can use rpc / literal. AFAIK rpc / encoded support is planned - not sure about 100% though.>> You can set your handler in your service.xml by:>> >> That is _not_ part of the operation - its one element below service, such as:>> > > > Execute Radio Commander> > > "false">com.siemens.swa.plugins.webservices.RCService > > > > > > Provided you have a module registed as soapmonitor. The user guide and migration guide have examples.>> HTH,> Robert> http://www.braziloutsource.com/ >>> On 3/15/06, SOA Work <[EMAIL PROTECTED]> wrote:>> Thx for your reply.>> Is> the only way to set Handlers ínside an operation > element? This would mean I have to write a lot more in my> deployment descriptor.>> I recently read a (german) article about axis2 which said rpc/encoded will still be supported (for backward compability). > Is it planned? Can I use rpc/literal f.e.? And how to configure this?>>> Thx> Dominik>>>> > -Ursprüngliche Nachricht-> > Von: axis-user@ws.apache.org> > Gesendet: 14.03.06 13:58:03> > An:> axis-user@ws.apache.org> > Betreff: Re: some axis2 deployment questions >> See my responses inline:> >> >> > On 3/14/06, SOA Work <[EMAIL PROTECTED]> wrote:>> >> > Hi,> >> > I'm going to publish a simple service using axis2 war distribution. > > Now I'm running into some (maybe simple) questions, which I can not solve with the user guide:> >> > 1) what's the difference between RawXML and RPC message receivers?>> > > > With> > RawXML the methods signature gets OMElement input and output? If I> > don't want to change my business class I have to use> > RPCMessageReceiver, right?> > > >> > I haven't used RPCMessageReceiver - but the version.aar does and it> > just returns a String - unlike the other recievers that use OMElement.> > RPCCallTest also works with Strings. > >> > 2)> > can I use patterns like: "*" or multiple operations names like>> > "getString getInt" to publish a bunch of operations?> >> > > > I believe just * is supported.> >> > 3)> > If I don't specify any operation inside my element all>> > operations are published. Can I set the messageReceiver to use for all > > operations?> >> > Not sure.> > 4) My resulting wsdl file is literal but I want ther rpc encoded style. How can I change this?>> >> > rpc encoded currently is not supported. > >> > thx a lot> > Dominik> > __> >> > Verschicken Sie romantische, coole und witzige Bilder per SMS! >> > Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193> >> >> >>>> __ >> Erweitern Sie FreeMail zu einem noch leistungsstärkeren E-Mail-Postfach!> Mehr Infos unter http://freemail.web.de/home/landingpad/?mc=021131 >>>__Verschicken Sie romantische, coole und witzige Bilder per SMS!Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193
Re: some axis2 deployment questions
Ok. How and where can I configure the style (rpc/literal f.e)? Sorry I made a mistake. I called the messageReceiver Handler. -> My question: Can I define a messageReceiver for all operations? If I want 20 operations to use the RPCMessageReceiver do I need 20 entries in my service element? Thx Dominik p.s.: Is there any dtd or xls file around for the service.xml? This would answer all my questions instantly ;-) > -Ursprüngliche Nachricht- > Von: axis-user@ws.apache.org > Gesendet: 15.03.06 14:51:21 > An: axis-user@ws.apache.org > Betreff: Re: some axis2 deployment questions You can use rpc / literal. AFAIK rpc / encoded support is planned - not sure about 100% though. > > You can set your handler in your service.xml by: > > > > That is _not_ part of the operation - its one element below service, such as: > > > > > Execute Radio Commander > > "false">com.siemens.swa.plugins.webservices.RCService > > class="org.apache.axis2.receivers.RawXMLINOutMessageReceiver"/> > > > > Provided you have a module registed as soapmonitor. The user guide and > migration guide have examples. > > HTH, > Robert > http://www.braziloutsource.com/ > > > On 3/15/06, SOA Work <[EMAIL PROTECTED]> wrote: > > Thx for your reply. > > Is > the only way to set Handlers ínside an operation > element? This would mean I have to write a lot more in my > deployment descriptor. > > I recently read a (german) article about axis2 which said rpc/encoded will > still be supported (for backward compability). > Is it planned? Can I use rpc/literal f.e.? And how to configure this? > > > Thx > Dominik > > > > > -Ursprüngliche Nachricht- > > Von: axis-user@ws.apache.org > > Gesendet: 14.03.06 13:58:03 > > An: > axis-user@ws.apache.org > > Betreff: Re: some axis2 deployment questions > > See my responses inline: > > > > > > On 3/14/06, SOA Work <[EMAIL PROTECTED]> wrote: > > > > > Hi, > > > > I'm going to publish a simple service using axis2 war distribution. > > Now I'm running into some (maybe simple) questions, which I can not solve > > with the user guide: > > > > 1) what's the difference between RawXML and RPC message receivers? > > > > > With > > RawXML the methods signature gets OMElement input and output? If I > > don't want to change my business class I have to use > > RPCMessageReceiver, right? > > > > > > I haven't used RPCMessageReceiver - but the version.aar does and it > > just returns a String - unlike the other recievers that use OMElement. > > RPCCallTest also works with Strings. > > > > 2) > > can I use patterns like: "*" or multiple operations names like > > > "getString getInt" to publish a bunch of operations? > > > > > > I believe just * is supported. > > > > 3) > > If I don't specify any operation inside my element all > > > operations are published. Can I set the messageReceiver to use for all > > operations? > > > > Not sure. > > 4) My resulting wsdl file is literal but I want ther rpc encoded style. > > How can I change this? > > > > > rpc encoded currently is not supported. > > > > thx a lot > > Dominik > > __ > > > > Verschicken Sie romantische, coole und witzige Bilder per SMS! > > > Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193 > > > > > > > > > __ > > Erweitern Sie FreeMail zu einem noch leistungsstärkeren E-Mail-Postfach! > Mehr Infos unter http://freemail.web.de/home/landingpad/?mc=021131 > > > __ Verschicken Sie romantische, coole und witzige Bilder per SMS! Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193
Re: some axis2 deployment questions
You can use rpc / literal. AFAIK rpc / encoded support is planned - not sure about 100% though. You can set your handler in your service.xml by: That is _not_ part of the operation - its one element below service, such as: name="RCService"> ref="soapmonitor"/> Execute Radio Commander name="ServiceClass" locked= "false">com.siemens.swa.plugins.webservices.RCService name="rcExecute"> class="org.apache.axis2.receivers.RawXMLINOutMessageReceiver"/> Provided you have a module registed as soapmonitor. The user guide and migration guide have examples. HTH, Robert http://www.braziloutsource.com/ On 3/15/06, SOA Work <[EMAIL PROTECTED]> wrote: Thx for your reply.Is the only way to set Handlers ínside an operation element? This would mean I have to write a lot more in my deployment descriptor.I recently read a (german) article about axis2 which said rpc/encoded will still be supported (for backward compability).Is it planned? Can I use rpc/literal f.e.? And how to configure this? ThxDominik> -Ursprüngliche Nachricht-> Von: axis-user@ws.apache.org> Gesendet: 14.03.06 13:58:03> An: axis-user@ws.apache.org> Betreff: Re: some axis2 deployment questionsSee my responses inline:>>> On 3/14/06, SOA Work <[EMAIL PROTECTED]> wrote: >> Hi,>> I'm going to publish a simple service using axis2 war distribution.> Now I'm running into some (maybe simple) questions, which I can not solve with the user guide:>> 1) what's the difference between RawXML and RPC message receivers? >> With> RawXML the methods signature gets OMElement input and output? If I> don't want to change my business class I have to use> RPCMessageReceiver, right?>>> I haven't used RPCMessageReceiver - but the version.aar does and it> just returns a String - unlike the other recievers that use OMElement.> RPCCallTest also works with Strings.>> 2)> can I use patterns like: "*" or multiple operations names like > "getString getInt" to publish a bunch of operations?>>> I believe just * is supported.>> 3)> If I don't specify any operation inside my element all > operations are published. Can I set the messageReceiver to use for all> operations?>> Not sure.> 4) My resulting wsdl file is literal but I want ther rpc encoded style. How can I change this? >> rpc encoded currently is not supported.>> thx a lot> Dominik> __>> Verschicken Sie romantische, coole und witzige Bilder per SMS! > Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193>>>__ Erweitern Sie FreeMail zu einem noch leistungsstärkeren E-Mail-Postfach!Mehr Infos unter http://freemail.web.de/home/landingpad/?mc=021131
Re: some axis2 deployment questions
Thx for your reply. Is the only way to set Handlers ínside an operation element? This would mean I have to write a lot more in my deployment descriptor. I recently read a (german) article about axis2 which said rpc/encoded will still be supported (for backward compability). Is it planned? Can I use rpc/literal f.e.? And how to configure this? Thx Dominik > -Ursprüngliche Nachricht- > Von: axis-user@ws.apache.org > Gesendet: 14.03.06 13:58:03 > An: axis-user@ws.apache.org > Betreff: Re: some axis2 deployment questions See my responses inline: > > > On 3/14/06, SOA Work <[EMAIL PROTECTED]> wrote: > > Hi, > > I'm going to publish a simple service using axis2 war distribution. > Now I'm running into some (maybe simple) questions, which I can not solve > with the user guide: > > 1) what's the difference between RawXML and RPC message receivers? > > With > RawXML the methods signature gets OMElement input and output? If I > don't want to change my business class I have to use > RPCMessageReceiver, right? > > > I haven't used RPCMessageReceiver - but the version.aar does and it > just returns a String - unlike the other recievers that use OMElement. > RPCCallTest also works with Strings. > > 2) > can I use patterns like: "*" or multiple operations names like > "getString getInt" to publish a bunch of operations? > > > I believe just * is supported. > > 3) > If I don't specify any operation inside my element all > operations are published. Can I set the messageReceiver to use for all > operations? > > Not sure. > 4) My resulting wsdl file is literal but I want ther rpc encoded style. How > can I change this? > > rpc encoded currently is not supported. > > thx a lot > Dominik > __ > > Verschicken Sie romantische, coole und witzige Bilder per SMS! > Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193 > > > __ Erweitern Sie FreeMail zu einem noch leistungsstärkeren E-Mail-Postfach! Mehr Infos unter http://freemail.web.de/home/landingpad/?mc=021131
Re: some axis2 deployment questions
See my responses inline:On 3/14/06, SOA Work <[EMAIL PROTECTED]> wrote: Hi,I'm going to publish a simple service using axis2 war distribution.Now I'm running into some (maybe simple) questions, which I can not solve with the user guide:1) what's the difference between RawXML and RPC message receivers? With RawXML the methods signature gets OMElement input and output? If I don't want to change my business class I have to use RPCMessageReceiver, right? I haven't used RPCMessageReceiver - but the version.aar does and it just returns a String - unlike the other recievers that use OMElement. RPCCallTest also works with Strings. 2) can I use patterns like: "*" or multiple operations names like "getString getInt" to publish a bunch of operations? I believe just * is supported. 3) If I don't specify any operation inside my element all operations are published. Can I set the messageReceiver to use for all operations? Not sure. 4) My resulting wsdl file is literal but I want ther rpc encoded style. How can I change this? rpc encoded currently is not supported. thx a lotDominik__ Verschicken Sie romantische, coole und witzige Bilder per SMS!Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193
some axis2 deployment questions
Hi, I'm going to publish a simple service using axis2 war distribution. Now I'm running into some (maybe simple) questions, which I can not solve with the user guide: 1) what's the difference between RawXML and RPC message receivers? With RawXML the methods signature gets OMElement input and output? If I don't want to change my business class I have to use RPCMessageReceiver, right? 2) can I use patterns like: "*" or multiple operations names like "getString getInt" to publish a bunch of operations? 3) If I don't specify any operation inside my element all operations are published. Can I set the messageReceiver to use for all operations? 4) My resulting wsdl file is literal but I want ther rpc encoded style. How can I change this? thx a lot Dominik __ Verschicken Sie romantische, coole und witzige Bilder per SMS! Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193
