Hello:I also have a similar requirement. Don't want to use the java classes but send raw SAOp XML and retrieve the RAW SOAP XML. How can I achieve this using AXIS2.
Regards, cabear On Thu, Jan 22, 2009 at 9:59 AM, Asensio, Rodrigo < [email protected]> wrote: > The best way to return raw xml data is using AXIOM I think > > Here is a snippet. > > public OMElement doSomething() { > OMFactory factory = OMAbstractFactory.getOMFactory(); > OMElement element = Factory.createElement(myNamespace, > "topelement"); > element.addAttribute("somekey", "somevalue"); > return element; > } > > Now, I think the services.xml should have as msg receivers these pair. > > > #message.receiver.inout=org.apache.axis2.receivers.RawXMLINOutMessageReceiver > > #message.receiver.inonly=org.apache.axis2.receivers.RawXMLINOnlyMessageReceiver > > > > > From: Kamal Chandana Mettananda [mailto:[email protected]] > Sent: Thursday, January 22, 2009 3:52 PM > To: [email protected] > Subject: Re: How to Return XML data from a webservice and how is it > consumed? > > Hi, > > Web service will return a SOAP xml file. By generating the client side > classes and using Axis you can map the resulting SOAP xml data into the > required class objects. > > > Kamal Mettananda > http://lkamal.blogspot.com > > On Thu, Jan 22, 2009 at 6:16 PM, Shravan Mahankali < > [email protected]> wrote: > Hi, > > Can anyone advise me, how return XML data from a webservice? > > Also, how a client consuming this service should interpret the output, I > mean what type of data can they expect? > > Thanks in advance. > > Thank You, > Shravan Kumar. M > ----------------------------- > > > > Please be advised that this email may contain confidential information. > If you are not the intended recipient, please do not read, copy or > re-transmit this email. If you have received this email in error, > please notify us by email by replying to the sender and by telephone > (call us collect at +1 202-828-0850) and delete this message and any > attachments. Thank you in advance for your cooperation and assistance. > > In addition, Danaher and its subsidiaries disclaim that the content of > this email constitutes an offer to enter into, or the acceptance of, > any > contract or agreement or any amendment thereto; provided that the > foregoing disclaimer does not invalidate the binding effect of any > digital or other electronic reproduction of a manual signature that is > included in any attachment to this email. >
