Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Message-ID: <44D32EC8.7040101@expertron.co.za>
Date: Fri, 04 Aug 2006 13:26:00 +0200
From: Justin Schoeman <justin@expertron.co.za>
User-Agent: Thunderbird 1.5.0.4 (X11/20060516)
MIME-Version: 1.0
To: axis-dev@ws.apache.org
Subject: Re: AW: [Axis2] Missing xsi:type in SOAP-Message
References: 
 <2D3131291B9ECA4D95C687463409067A028FAF76@ms2exchange.ms2.iitb.fraunhofer.de>
	 <44D2ED87.6090404@expertron.co.za>
 <19e0530f0608040349m2e013b56q3429b7f02b5047ec@mail.gmail.com>
In-Reply-To: <19e0530f0608040349m2e013b56q3429b7f02b5047ec@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable

AXIS2-455 as well. I tried to open another one, but Jira kept on timing=20
out. Completely forgot to repost it :-( . Also had many on-list=20
discussions, but have never managed to find any solutions.

Axis2 is really awesome, but it does seem to have a number of problems=20
with inherited types, and even more when interoperating with dotNET with =

inherited types...

-justin

Davanum Srinivas wrote:
> Justin,
>=20
> I see only 1 issue from you which is AXIS2-586. Are there others?
>=20
> -- dims
>=20
> On 8/4/06, Justin Schoeman <justin@expertron.co.za> wrote:
>> Abandon all hope ye who enter here ;-) ...
>>
>> Even when you get xsi:type working, deserialisation is also completely=

>> broken.  I have opened a number of Jira's on these issues, but never h=
ad
>> much luck.  Tried to debug it myself too, but failed miserably.
>>
>> If you have any better luck, please let me know!
>>
>> -justin
>>
>>
>> Desiree Hilbring wrote:
>> > Hello,
>> >
>> > thanks, I tried the latest nightly, but there I get false code=20
>> created by WSDL2Java (I created a bug).
>> >
>> >    [javac] Compiling 225 source files to=20
>> C:\hilbring\EclipseWTP\GMLSFE\classes
>> >     [javac]=20
>> C:\hilbring\EclipseWTP\GMLSFE\output\src\org\example\types\GMLSFEStub.=
java:142:=20
>> toEnvelope(org.apache.axiom.soap.SOAPFactory) in=20
>> org.example.types.GMLSFEStub cannot be applied to=20
>> (org.apache.axiom.soap.SOAPFactory,orchestra.oas.building.BuildingStri=
ngDocument,boolean)=20
>>
>> >     [javac] env =3D=20
>> toEnvelope(getFactory(_operationClient.getOptions().getSoapVersionURI(=
)),
>> >     [javac] ^
>> >     [javac]=20
>> C:\hilbring\EclipseWTP\GMLSFE\output\src\org\example\types\GMLSFEStub.=
java:247:=20
>> toEnvelope(org.apache.axiom.soap.SOAPFactory) in=20
>> org.example.types.GMLSFEStub cannot be applied to=20
>> (org.apache.axiom.soap.SOAPFactory,orchestra.oas.building.BuildingStri=
ngDocument,boolean)=20
>>
>> >     [javac] env =3D=20
>> toEnvelope(getFactory(_operationClient.getOptions().getSoapVersionURI(=
)),
>> >     [javac] ^
>> >
>> > Another issue I detected with 1.0 version is, that even, if the=20
>> xsi:type is sent, the inheritance has problems with underlines in=20
>> typenames.
>> > the attachment includes a little inheritance example,=20
>> OA_MIFASCapabilitesType is derived from=20
>> OAMIServiceSpecificCapabilites. To send the xsi:type in the=20
>> SOAP-Message I am still using the following lines:
>> > XmlCursor cur =3D=20
>> resp.getOAGetMetaInformationResponse().getFeatureMetaInformation().get=
OAMIServiceSpecificCapabilities().newCursor();=20
>>
>> > cur.toFirstChild();
>> >=20
>> cur.insertAttributeWithValue("type","http://www.w3.org/2001/XMLSchema-=
instance","OAMIFASCapabilitiesType");=20
>>
>> > cur.dispose();
>> > The SOAP-Message does include the xsi:type but the client does not=20
>> recognize the subtype OA_MIFASCapabilitiesType.
>> > But changing the name of OA_MIFASCapabilitiesType in=20
>> delivery060803-2.xsd to OAMIFASCapabilitiesType will solve the problem=
=20
>> and the example will work.
>> > Is it possible to use underlines in the typeNames or are there any=20
>> restrictions, or is this a bug?
>> >
>> > Greetings Desiree
>> >
>> >> -----Urspr=FCngliche Nachricht-----
>> >> Von: Davanum Srinivas [mailto:davanum@gmail.com]
>> >> Gesendet: Donnerstag, 3. August 2006 15:27
>> >> An: axis-dev@ws.apache.org
>> >> Betreff: Re: [Axis2] Missing xsi:type in SOAP-Message
>> >>
>> >> This should work in latest nightly. If not, please log a bug.
>> >>
>> >> thanks,
>> >> dims
>> >>
>> >> On 8/3/06, Desiree Hilbring
>> >> <Desiree.Hilbring@iitb.fraunhofer.de> wrote:
>> >>> Hello,
>> >>>
>> >>> I am trying to create an working inheritance example with Axis2. I=
n
>> >>> the attached example case OAMIFASCapabilitiesType is derived from
>> >>> OAMIServiceSpecificCapabilities.
>> >>> To recognize the inheritance the client needs the xsi:type
>> >> in the SOAP
>> >>> message, but it is missing as you can see trying the
>> >> attached example.
>> >>> The example will work outcommenting the following lines in
>> >>> GMLSFESkeleton:
>> >>>
>> >>> XmlCursor cur =3D
>> >>>
>> >> resp.getOAGetMetaInformationResponse().getFeatureMetaInformation().=
get
>> >>> OA MIServiceSpecificCapabilities().newCursor();
>> >>> cur.toFirstChild();
>> >>>
>> >> cur.insertAttributeWithValue("type","http://www.w3.org/2001/XMLSche=
ma-
>> >>> in
>> >>> stance","OAMIFASCapabilitiesType");
>> >>> cur.dispose();
>> >>>
>> >>> Why is the xsi:type not sent? Is this a bug?
>> >>>
>> >>> Greetings Desiree
>> >>>
>> >>>
>> >>>
>> >> -------------------------------------------------------------------=
--
>> >>> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
>> >>> For additional commands, e-mail: axis-dev-help@ws.apache.org
>> >>>
>> >>>
>> >>>
>> >>
>> >> --
>> >> Davanum Srinivas : http://www.wso2.net (Oxygen for Web
>> >> Service Developers)
>> >>
>> >> -------------------------------------------------------------------=
--
>> >> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
>> >> For additional commands, e-mail: axis-dev-help@ws.apache.org
>> >>
>> >>
>> >>
>> >>=20
>> ----------------------------------------------------------------------=
--
>> >>
>> >> -------------------------------------------------------------------=
--
>> >> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
>> >> For additional commands, e-mail: axis-dev-help@ws.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-dev-help@ws.apache.org
>>
>>
>=20
>=20


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org