Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 67066 invoked from network); 23 Sep 2008 14:53:26 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 23 Sep 2008 14:53:26 -0000 Received: (qmail 99786 invoked by uid 500); 23 Sep 2008 14:53:21 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 99737 invoked by uid 500); 23 Sep 2008 14:53:21 -0000 Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-dev@ws.apache.org Received: (qmail 99726 invoked by uid 99); 23 Sep 2008 14:53:21 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Sep 2008 07:53:21 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of mgainty@hotmail.com designates 65.55.116.113 as permitted sender) Received: from [65.55.116.113] (HELO blu0-omc3-s38.blu0.hotmail.com) (65.55.116.113) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Sep 2008 14:52:20 +0000 Received: from BLU142-W40 ([65.55.116.73]) by blu0-omc3-s38.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 23 Sep 2008 07:52:47 -0700 Message-ID: Content-Type: multipart/alternative; boundary="_4ff06265-b8ff-4886-8374-c2c552ff11f7_" X-Originating-IP: [66.31.231.31] From: Martin Gainty To: Subject: RE: SOAPEnvelope deserialization error for in-only operations Date: Tue, 23 Sep 2008 10:52:46 -0400 Importance: Normal In-Reply-To: <7DB66A1A-D425-4D1C-ACB9-E6B5E696B342@enviromatics.net> References: <7DB66A1A-D425-4D1C-ACB9-E6B5E696B342@enviromatics.net> MIME-Version: 1.0 X-OriginalArrivalTime: 23 Sep 2008 14:52:47.0157 (UTC) FILETIME=[0ADBBE50:01C91D8C] X-Virus-Checked: Checked by ClamAV on apache.org --_4ff06265-b8ff-4886-8374-c2c552ff11f7_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable 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.EchoStringParamDocum= ent param)// This method will handle the serialization. public static org.apache.xmlbeans.XmlObject fromOM(org.apache.axis2.om.OMElement param=2C java.lang.Class type) //This method will handle the de-serialization. Martin=20 ______________________________________________=20 Disclaimer and confidentiality note=20 Everything in this e-mail and any attachments relates to the official busin= ess of Sender. This transmission is of a confidential nature and Sender doe= s not endorse distribution to any party other than intended recipient. Send= er does not necessarily endorse content contained within this transmission.= =20 > To: axis-dev@ws.apache.org > From: martin.scholl@enviromatics.net > Subject: SOAPEnvelope deserialization error for in-only operations > Date: Tue=2C 23 Sep 2008 16:12:58 +0200 >=20 > Hi all=2C >=20 > I'm stuck with some strange issue about envelope deserialization when =20 > performing in-only operations. I have to access the SOAPEnvelope from =20 > within the ServiceSkeleton implementation class. The envelope =20 > contained in the MessageContext is non-null and it seems to be valid =20 > because XMLBeans parameter is correct. Nevertheless if I call toString=20 > () method on the envelope object an OMException=2C caused by a =20 > NoSuchElementException is thrown. I also tried to convert the =20 > envelope to an org.w3c.dom.Element but calling toString on this =20 > object I receive a RuntimeException with message 'Can not serialize =20 > OM Element Envelope'=2C caused by a XMLStreamException. > This phenomenon looks rather strange to me because this is only true =20 > for in-only operations and XMLBeans CAN build a valid object from the =20 > SOAPBody in any case. Furthermore the envelope of in-out operations =20 > is all valid. >=20 > I use Axis2 1.4.1 on top of Tomcat 6.0.14 and generate the service =20 > client and server classes from WSDL 1.1 using WSDL2Java and XMLBeans =20 > 2.3.0. >=20 > I found some issues about deserialization of the envelope. Could =20 > there be any relation? Does anyone have a clue what could solve this =20 > issue since I already posted on axis-user but nobody could help me =20 > there and I need a solution to finish my current work. Therefore any =20 > help is very much appreciated. >=20 > Thanks in advance. >=20 > Regards=2C >=20 > Martin >=20 >=20 >=20 > PS: > Two additional questions: >=20 > - I'm wondering why WSDL2Java generates a service.xml which states =20 > that the MEP for in-only operations is "robust-in-only" since I'm =20 > using WSDL1.1 and as far as I know WSDL1.1 is not capable of that?!? =20 > Am I wrong with that? > - I'm also wondering why the AbstractRobustInOnlyMessageReceiver and =20 > the AbstractInOutSyncMessageReceiver is used for robust-in-only and =20 > in-out mep=2C respectively=2C since both are deprecated? But this seems = =20 > to be not that much of an issue... >=20 > PPS: > If you miss any information please let me know. >=20 > --------------------------------------------------------------------- > To unsubscribe=2C e-mail: axis-dev-unsubscribe@ws.apache.org > For additional commands=2C e-mail: axis-dev-help@ws.apache.org >=20 _________________________________________________________________ Stay up to date on your PC=2C the Web=2C and your mobile phone with Windows= Live. http://clk.atdmt.com/MRT/go/msnnkwxp1020093185mrt/direct/01/= --_4ff06265-b8ff-4886-8374-c2c552ff11f7_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Martin-

please verify WSDL2Java produces stub containing toOM and fr= omOM methods
(there was an bug with 0.95 version that was supposedly fix= ed)
http://issues.apache.org/jira/browse/AXIS2-515

WSDL2JAVA shou= ld produce something like
public static
org.apache.axiom.om.OMElement= toOM(org.soapinterop.xsd.EchoStringParamDocument
param)// This method w= ill handle the serialization.

public static org.apache.xmlbeans.XmlO= bject
fromOM(org.apache.axis2.om.OMElement param=2C java.lang.Class type= ) //This
method will handle the de-serialization.

Martin
____= __________________________________________
Disclaimer and confidentiali= ty note
Everything in this e-mail and any attachments relates to the of= ficial business of Sender. This transmission is of a confidential nature an= d Sender does not endorse distribution to any party other than intended rec= ipient. Sender does not necessarily endorse content contained within this t= ransmission.


>=3B To: axis-dev@ws.apache.org
>=3B From: = martin.scholl@enviromatics.net
>=3B Subject: SOAPEnvelope deserializat= ion error for in-only operations
>=3B Date: Tue=2C 23 Sep 2008 16:12:5= 8 +0200
>=3B
>=3B Hi all=2C
>=3B
>=3B I'm stuck with = some strange issue about envelope deserialization when
>=3B performi= ng in-only operations. I have to access the SOAPEnvelope from
>=3B w= ithin the ServiceSkeleton implementation class. The envelope
>=3B co= ntained in the MessageContext is non-null and it seems to be valid
>= =3B because XMLBeans parameter is correct. Nevertheless if I call toString =
>=3B () method on the envelope object an OMException=2C caused by a =
>=3B NoSuchElementException is thrown. I also tried to convert the <= br>>=3B envelope to an org.w3c.dom.Element but calling toString on this =
>=3B object I receive a RuntimeException with message 'Can not serial= ize
>=3B OM Element Envelope'=2C caused by a XMLStreamException.
= >=3B This phenomenon looks rather strange to me because this is only true=
>=3B for in-only operations and XMLBeans CAN build a valid object f= rom the
>=3B SOAPBody in any case. Furthermore the envelope of in-ou= t operations
>=3B is all valid.
>=3B
>=3B I use Axis2 1.4= .1 on top of Tomcat 6.0.14 and generate the service
>=3B client and = server classes from WSDL 1.1 using WSDL2Java and XMLBeans
>=3B 2.3.0= .
>=3B
>=3B I found some issues about deserialization of the env= elope. Could
>=3B there be any relation? Does anyone have a clue wha= t could solve this
>=3B issue since I already posted on axis-user bu= t nobody could help me
>=3B there and I need a solution to finish my= current work. Therefore any
>=3B help is very much appreciated.
= >=3B
>=3B Thanks in advance.
>=3B
>=3B Regards=2C
>= =3B
>=3B Martin
>=3B
>=3B
>=3B
>=3B PS:
>= =3B Two additional questions:
>=3B
>=3B - I'm wondering why WSDL= 2Java generates a service.xml which states
>=3B that the MEP for in-= only operations is "robust-in-only" since I'm
>=3B using WSDL1.1 and= as far as I know WSDL1.1 is not capable of that?!?
>=3B Am I wrong = with that?
>=3B - I'm also wondering why the AbstractRobustInOnlyMessa= geReceiver and
>=3B the AbstractInOutSyncMessageReceiver is used for= robust-in-only and
>=3B in-out mep=2C respectively=2C since both ar= e deprecated? But this seems
>=3B to be not that much of an issue...=
>=3B
>=3B PPS:
>=3B If you miss any information please let= me know.
>=3B
>=3B --------------------------------------------= -------------------------
>=3B To unsubscribe=2C e-mail: axis-dev-unsu= bscribe@ws.apache.org
>=3B For additional commands=2C e-mail: axis-dev= -help@ws.apache.org
>=3B

Stay up to date on your PC=2C= the Web=2C and your mobile phone with Windows Live. See Now<= /a> = --_4ff06265-b8ff-4886-8374-c2c552ff11f7_--