On Mon=2C F= eb 9=2C 2009 at 11:43 PM=2C Chandra suriya pandian=2C Sathish (GE Infra=2C = Energy) <=3Bs= athish.chandra@ge.com>=3B wrote:

Thanks=20 Keith.

= =3B

I am=20 able to get through that error by changing the type to xs:any.=20

But =3Bnow= i am getting the =3Bfollowing exception under the same=20 scenario:

= =3B

Caused by:
com.ctc.wstx.exc.WstxParsingException: Expected a text token=2C got START_ELEMENT.
at [row=2Ccol {unknown= -source}]:=20 [1=2C208]

at=20 com.ctc.wstx.sr.StreamScanner.constructWfcException(StreamScanner.java:605)

at com.ctc.wstx.sr.StreamScanner.throwParseError(StreamScanner.java:461)

at=20 com.ctc.wstx.sr.BasicStreamReader.getElementText(BasicStreamReader.java:677)
at org.apache.axiom.om.impl.llom.OMStAXWrapper.getElementText(OMStAXWrapper.java:899)

= =3B

Any=20 idea =3Bon the above problem.

=3B
Regards=2C

Sathish Chandra =3B
=3B

=3B

From: keith chapman=20 [mailto:keithgchapman@gmail.com<= /a>]
Sent: 09 February 2009=20 16:29
To: axis-user@ws= .apache.org
Subject: Re: Issue with=20 Axis OMElement

Hi=2C

This is due to a bug in Axis2. Ideally an OMElement= should=20 map to xs:any and not xs:anyType in the WSDL. Therefore the workaround I co= uld=20 suggest is this=2C Save the WSDL and edit it to use xs:any instead of=20 xs:anyType.

Thanks=2C
Keith.

On Mon=2C Feb 9=2C 2009 at 8:30 PM=2C Chandra= suriya pandian=2C=20 Sathish (GE Infra=2C Energy) <=3Bsathish.chandra@ge.com>=3B=20 wrote:

Hi=2C
>=3B=20 I have WebService enabled a service method that returns OMElement. The>=3B=20 generated WSDL shows the element type as 'anyType'.
>=3B
>=3B I= =20 generated a stub from the WSDL and executed a client invoking the
>= =3B=20 WebService method through the stub.
>=3B
>=3B The HTTP trace sh= ows the=20 response stream returned by WebService is
>=3B correct.
>=3B Bu= t in the=20 client I am getting the following error:
>=3B
>=3B=20 org.apache.axis2.databinding.ADBException: Any type element type has
&= gt=3B=20 not been given
>=3B =3B =3B =3B at
>=3B=20 org.apache.axis2.databinding.utils.ConverterUtil.getAnyTypeObject(Conv>=3B=20 erterUtil.java:1612)
>=3B
>=3B Exerpt from WSDL is:
>=3B>=3B=20 <=3Bxs:element name=3D"mtomSampleResponse">=3B
>=3B=20 <=3Bxs:complexType>=3B<=3Bxs:sequence>=3B
>=3B <=3Bxs:elem= ent minOccurs=3D"0"=20 name=3D"return" nillable=3D"true"
>=3B type=3D"xs:anyType"/>=3B>=3B=20 <=3B/xs:sequence>=3B<=3B/xs:complexType>=3B
>=3B=20 <=3B/xs:element>=3B
>=3B
>=3B Exerpt from the response stre= am=20 is:
>=3B
>=3B <=3B?xml version=3D'1.0' encoding=3D'UTF-8'?>= =3B
>=3B=20 <=3Bsoapenv:Envelope
>=3B xmlns:soapenv=3D"http://www.w3.org/2003/05/soap-envelope"&g= t=3B<=3Bsoapenv:Body>=3B
>=3B=20 <=3Bns:mtomSampleResponse
>=3B xmlns:ns=3D"http://ws.apache.org/axis2">=3B<=3Bns:return>=3B<= br>>=3B=20 <=3Breturn>=3B<=3Bxop:Include
>=3B href=3D"cid:1.urn:uuid:49= F67B152B605353D81233939394759@apache.org"
>=3B=20 xmlns:xop=3D"http://www= .w3.org/2004/08/xop/include"=20 />=3B<=3B/return>=3B
>=3B=20 <=3B/ns:return>=3B<=3B/ns:mtomSampleResponse>=3B
>=3B=20 <=3B/soapenv:Body>=3B<=3B/soapenv:Envelope>=3B
>=3B
>= =3B Could you=20 please kindly look into the same and let me know how I can
>=3B over= come=20 the above problem.
>=3B Do I have to configure anything to map the r= esponse=20 element of type
>=3B 'anyType' anywhere to construct 'OMElement'=20 back.
>=3B
I am using Axis 2-1.4.1.

>=3B Regards=2C<= br>>=3B=20 Sathish Chandra
>=3B

--
Keith=20 Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Ser= vice=20 Platform.
http://wso2.org/

blog:= http://www.keith-chapman.org<= br>