Hi,
I think this either has to do with AXIOM serialization or the pull
parser returned by XMLbeans. As I presume what happens here is a wrong
serialization of the XMLbeans object and since that serialization
happens through the XMLStreamReader returned by XMLBeans, the problem
either has to do with the AXIOM tree or the returned stream reader
implementation.
On 8/4/06, Justin Schoeman <[EMAIL PROTECTED]> wrote:
AXIS2-455 as well. I tried to open another one, but Jira kept on timing
out. Completely forgot to repost it :-( . Also had many on-list
discussions, but have never managed to find any solutions.
Axis2 is really awesome, but it does seem to have a number of problems
with inherited types, and even more when interoperating with dotNET with
inherited types...
-justin
Davanum Srinivas wrote:
> Justin,
>
> I see only 1 issue from you which is AXIS2-586. Are there others?
>
> -- dims
>
> On 8/4/06, Justin Schoeman <[EMAIL PROTECTED]> 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 had
>> 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
>> created by WSDL2Java (I created a bug).
>> >
>> > [javac] Compiling 225 source files to
>> C:\hilbring\EclipseWTP\GMLSFE\classes
>> > [javac]
>>
C:\hilbring\EclipseWTP\GMLSFE\output\src\org\example\types\GMLSFEStub.java:142:
>> toEnvelope(org.apache.axiom.soap.SOAPFactory) in
>> org.example.types.GMLSFEStub cannot be applied to
>>
(org.apache.axiom.soap.SOAPFactory,orchestra.oas.building.BuildingStringDocument,boolean)
>>
>> > [javac] env =
>> toEnvelope(getFactory(_operationClient.getOptions().getSoapVersionURI()),
>> > [javac] ^
>> > [javac]
>>
C:\hilbring\EclipseWTP\GMLSFE\output\src\org\example\types\GMLSFEStub.java:247:
>> toEnvelope(org.apache.axiom.soap.SOAPFactory) in
>> org.example.types.GMLSFEStub cannot be applied to
>>
(org.apache.axiom.soap.SOAPFactory,orchestra.oas.building.BuildingStringDocument,boolean)
>>
>> > [javac] env =
>> toEnvelope(getFactory(_operationClient.getOptions().getSoapVersionURI()),
>> > [javac] ^
>> >
>> > Another issue I detected with 1.0 version is, that even, if the
>> xsi:type is sent, the inheritance has problems with underlines in
>> typenames.
>> > the attachment includes a little inheritance example,
>> OA_MIFASCapabilitesType is derived from
>> OAMIServiceSpecificCapabilites. To send the xsi:type in the
>> SOAP-Message I am still using the following lines:
>> > XmlCursor cur =
>>
resp.getOAGetMetaInformationResponse().getFeatureMetaInformation().getOAMIServiceSpecificCapabilities().newCursor();
>>
>> > cur.toFirstChild();
>> >
>>
cur.insertAttributeWithValue("type","http://www.w3.org/2001/XMLSchema-instance","OAMIFASCapabilitiesType";);
>>
>> > cur.dispose();
>> > The SOAP-Message does include the xsi:type but the client does not
>> recognize the subtype OA_MIFASCapabilitiesType.
>> > But changing the name of OA_MIFASCapabilitiesType in
>> delivery060803-2.xsd to OAMIFASCapabilitiesType will solve the problem
>> and the example will work.
>> > Is it possible to use underlines in the typeNames or are there any
>> restrictions, or is this a bug?
>> >
>> > Greetings Desiree
>> >
>> >> -----Ursprüngliche Nachricht-----
>> >> Von: Davanum Srinivas [mailto:[EMAIL PROTECTED]
>> >> Gesendet: Donnerstag, 3. August 2006 15:27
>> >> An: [email protected]
>> >> 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
>> >> <[EMAIL PROTECTED]> wrote:
>> >>> Hello,
>> >>>
>> >>> I am trying to create an working inheritance example with Axis2. In
>> >>> 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 =
>> >>>
>> >> resp.getOAGetMetaInformationResponse().getFeatureMetaInformation().get
>> >>> OA MIServiceSpecificCapabilities().newCursor();
>> >>> cur.toFirstChild();
>> >>>
>> >> cur.insertAttributeWithValue("type","http://www.w3.org/2001/XMLSchema-
>> >>> in
>> >>> stance","OAMIFASCapabilitiesType");
>> >>> cur.dispose();
>> >>>
>> >>> Why is the xsi:type not sent? Is this a bug?
>> >>>
>> >>> Greetings Desiree
>> >>>
>> >>>
>> >>>
>> >> ---------------------------------------------------------------------
>> >>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> >>> For additional commands, e-mail: [EMAIL PROTECTED]
>> >>>
>> >>>
>> >>>
>> >>
>> >> --
>> >> Davanum Srinivas : http://www.wso2.net (Oxygen for Web
>> >> Service Developers)
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> >> For additional commands, e-mail: [EMAIL PROTECTED]
>> >>
>> >>
>> >>
>> >>
>> ------------------------------------------------------------------------
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> >> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Ajith Ranabahu
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
