Martin- please verify WSDL2Java produces stub containing toOM and fromOM methods (there was an bug with 0.95 version that was supposedly fixed) http://issues.apache.org/jira/browse/AXIS2-515
WSDL2JAVA should produce something like public static org.apache.axiom.om.OMElement toOM(org.soapinterop.xsd.EchoStringParamDocument param)// This method will handle the serialization. public static org.apache.xmlbeans.XmlObject fromOM(org.apache.axis2.om.OMElement param, java.lang.Class type) //This method will handle the de-serialization. Martin ______________________________________________ Disclaimer and confidentiality note Everything in this e-mail and any attachments relates to the official business of Sender. This transmission is of a confidential nature and Sender does not endorse distribution to any party other than intended recipient. Sender does not necessarily endorse content contained within this transmission. > To: axis-dev@ws.apache.org > From: [EMAIL PROTECTED] > Subject: SOAPEnvelope deserialization error for in-only operations > Date: Tue, 23 Sep 2008 16:12:58 +0200 > > Hi all, > > I'm stuck with some strange issue about envelope deserialization when > performing in-only operations. I have to access the SOAPEnvelope from > within the ServiceSkeleton implementation class. The envelope > contained in the MessageContext is non-null and it seems to be valid > because XMLBeans parameter is correct. Nevertheless if I call toString > () method on the envelope object an OMException, caused by a > NoSuchElementException is thrown. I also tried to convert the > envelope to an org.w3c.dom.Element but calling toString on this > object I receive a RuntimeException with message 'Can not serialize > OM Element Envelope', caused by a XMLStreamException. > This phenomenon looks rather strange to me because this is only true > for in-only operations and XMLBeans CAN build a valid object from the > SOAPBody in any case. Furthermore the envelope of in-out operations > is all valid. > > I use Axis2 1.4.1 on top of Tomcat 6.0.14 and generate the service > client and server classes from WSDL 1.1 using WSDL2Java and XMLBeans > 2.3.0. > > I found some issues about deserialization of the envelope. Could > there be any relation? Does anyone have a clue what could solve this > issue since I already posted on axis-user but nobody could help me > there and I need a solution to finish my current work. Therefore any > help is very much appreciated. > > Thanks in advance. > > Regards, > > Martin > > > > PS: > Two additional questions: > > - I'm wondering why WSDL2Java generates a service.xml which states > that the MEP for in-only operations is "robust-in-only" since I'm > using WSDL1.1 and as far as I know WSDL1.1 is not capable of that?!? > Am I wrong with that? > - I'm also wondering why the AbstractRobustInOnlyMessageReceiver and > the AbstractInOutSyncMessageReceiver is used for robust-in-only and > in-out mep, respectively, since both are deprecated? But this seems > to be not that much of an issue... > > PPS: > If you miss any information please let me know. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > _________________________________________________________________ Stay up to date on your PC, the Web, and your mobile phone with Windows Live. http://clk.atdmt.com/MRT/go/msnnkwxp1020093185mrt/direct/01/
