If someone is using
Axis2's ServiceClient to send a request to a service they will have to deal with OMElements. That is because ServiceClient accepts the payload as a OMElement. Using
Axiom API's to create this OMElement could be time consuming and may take several lines of code. Alternatively users could create this OMElement from a String as follows,
OMElement payload = AXIOMUtil.stringToOM("Hi! This is a sample Request.");
This utility method that comes with
Axiom takes in a String as the argument and returns an OMElement.
14 comments:
Very useful tip, it save my time.
Thanks for the tip. Helped me to no end.
very useful, i spent a lot of time searching the way to transform string to omelement, because in the project that i´m working we have to deal with axis2, a dark world, thanks for your light ;-)
Many thanks, saved me a lot of time.
Thank you very much. This save me amount of time.
Awesome tip! Certainly was going to save half an hour of coding at least. :)
very useful comment.thanks.
Very useful I was wondering all day how to create one..
Thanks
Quite useful tip. tx!
i heard that there are performance problems in using toStringOM() stuff.
1) It does not work with SOAP messages with attachments ( MTOM & XOP).
2) The other one being, that the same OMElement object is being read/prepared twice.
when JIBX is used as a DataBinding framework
Is it true ? Any help is appreciated
Thank you, very much
Thank YOu !!!!
Thank YOu !!!!
It helped me a lot man. saved a week of time.
Post a Comment