Is it possible to write custom serializers or deserializers for axis2? Like in axis? So that I can use all classes, even those which aren't javabeans.
> -----Ursprüngliche Nachricht----- > Von: [email protected] > Gesendet: 30.03.06 06:59:00 > An: [email protected] > Betreff: Re: [Axis2] Converting 1.x RPC to 2.0 Document style > Hi Ttrevor > > RPCMessgeReciver or any other messageReciver in Axis2 can not deal with > org.w3c.dom.Document , so I think you have to modify your service class > to return OM element , or you have to write you own message receiver to > deal with this case. But I think easy way is to just return OMElement , > any simple type or any JavaBean from service class, then > RPCMessageReciver can handle that. > > So pls try that and if you have any q pls drop a mail. :) > > > trevor paterson (RI) wrote: > > >The original method returned an instance of an XML Document: > > > >public org.w3c.dom.Document; getChromosomes(String SpeciesAccession, String > >SpeciesName, String SpeciesLatinName ) throws java.rmi.RemoteException > > > >If I make a service using this method by deploying with a services.xml file > >(below) the service deploys ok, but always throws an error when run > > > >If I change the method to return an OMElement and add the Document node to > >the OMElement in the method body the service works ok, and I just have to > >extract the Document from the OMElement. > > > >I guess I just don't know how to specify the services.xml correctly to > >deploy a service returning anything but an OMElement - and can find no > >documentation on this....my services.xml is below: I don't feel confident to > >write my own wsdl.... > > > ><service name="GetCGKaryotypeView"> > > <description> > > refactored service for getting karyotype for a species through the > > current Ark on axis 1.2 to 2.0. > > </description> > > <module ref="logging"/> > > <parameter name="ServiceClass" > > locked="false">org.thearkdb.services2.ReturnCGKaryotypeView</parameter> > > <operation name="getChromosomes"> > > <messageReceiver > > class="org.apache.axis2.rpc.receivers.RPCMessageReceiver"/> > > </operation> > ></service> > > > > > >Ta > > > >trevor > > > >-----Original Message----- > >From: SOA Work [mailto:[EMAIL PROTECTED] > >Sent: 27 March 2006 16:45 > >To: [email protected] > >Subject: RE: [Axis2] Converting 1.x RPC to 2.0 Document style > > > > > >Hm, so your original method returned a java class. For example a bean? > >So what problem do you have with the return value? > > > > > > > >>-----Ursprüngliche Nachricht----- > >>Von: [email protected] > >>Gesendet: 27.03.06 16:51:44 > >>An: <[email protected]> > >>Betreff: RE: [Axis2] Converting 1.x RPC to 2.0 Document style > >> > >> > > > > > > > > > >>Yes > >> > >>I am getting there - I can invoke the server method OK - the server code > >>executes OK but am having trouble returning the results as a Document. > >> > >>Maybe I need to chenge my methods to create and return an OMElement instead > >>of Document? > >> > >>trevor > >> > >>-----Original Message----- > >>From: SOA Work [mailto:[EMAIL PROTECTED] > >>Sent: 27 March 2006 15:48 > >>To: [email protected] > >>Subject: Re: [Axis2] Converting 1.x RPC to 2.0 Document style > >> > >> > >>I'm not sure if I understand the question right. But try using your > >>existing service class with axis2 and the RPCMessageReceiver. > >>RPCMessageReceiver is used to map the xml data to java objects. I think > >>this is what you want. > >>The wsdl is generated. > >> > >>RPCMessageReceiver means RPC programming model, not the wsdl style (which > >>can be document). > >>This article descripes the different wsdl styles and the difference to the > >>programming model: > >>http://www-128.ibm.com/developerworks/webservices/library/ws-whichwsdl > >>/ > >> > >>I hope this helps. > >> > >> > >> > >> > >>>-----Ursprüngliche Nachricht----- > >>>Von: [email protected] > >>>Gesendet: 27.03.06 14:21:38 > >>>An: <[email protected]> > >>>Betreff: [Axis2] Converting 1.x RPC to 2.0 Document style > >>> > >>> > >> > >> > >>>I have used java:RPC style SOAP messaging in axis 1.2 and now want to > >>>migrate to axis2 - where as I understand it Document style messaging is > >>>preferred. > >>> > >>> > >>> > >>>I can't find any documentation on how to create the wsdl to map to the > >>>methodName(parameterX, parameterY) of my service. > >>> > >>> > >>> > >>>Do I have to write a bespoke receiver that takes the OMElement apart and > >>>calls the service method with the correct parameters - or can this be done > >>>'automatically' by creating an appropriate service.xml, using either the > >>>RawXMLINOutMessageReceiver or the RPCMessageReceiver? > >>> > >>> > >>> > >>>thanks for any help > >>> > >>>Trevor Paterson > >>> > >>>Roslin Institute > >>> > >>> > >>> > >>> > >>> > >>> > >>__________________________________________________________________________ > >>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 > > > > > > > > > > > > -- > Thanks, > Deepal > ................................................................ > ~Future is Open~ > > ______________________________________________________________ Verschicken Sie romantische, coole und witzige Bilder per SMS! Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193
