You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Thilina Gunarathne (JIRA)" <ji...@apache.org> on 2005/07/05 10:07:12 UTC
[jira] Resolved: (AXIS2-62) Serilizing Envelopes with multiple optimized contents.
[ http://issues.apache.org/jira/browse/AXIS2-62?page=all ]
Thilina Gunarathne resolved AXIS2-62:
-------------------------------------
Resolution: Fixed
Altered StAXSoapModelBuilder. When an END_ELEMENT event is return from the XMLStAX parser at the point of setting complete (line 327) earlier it casted the lastNode to a OMElement., which prevented OMText being a lastNode. Changed it so that it'll be casted to a Node.
OMNode e = (OMNode) lastNode;
Also altered MTOMStAXSOAPModelBuilder so that it'l not set complete the OMText's at the point of creating.
> Serilizing Envelopes with multiple optimized contents.
> ------------------------------------------------------
>
> Key: AXIS2-62
> URL: http://issues.apache.org/jira/browse/AXIS2-62
> Project: Apache Axis 2.0 (Axis2)
> Type: Bug
> Reporter: Thilina Gunarathne
> Assignee: Thilina Gunarathne
>
> <my:data>
> <my:subData>
> <xop:Include href="cid:2-2846124687180564971@schemas.xmlsoap.org" xmlns:xop="http://www.w3.org/2004/08/xop/Include"></xop:Include>
> </my:subData>
> <my:subData>
> <xop:Include href="cid:25194435278458331510@schemas.xmlsoap.org" xmlns:xop="http://www.w3.org/2004/08/xop/Include"></xop:Include>
> </my:subData>
> </my:data>
> When handling the above XML MTOMSoapModelBuilder creates the OM tree like follows.
> Element my:data has olny one subData child. Next subData child is lost in the OM tree.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[Axis2] Re: [jira] Resolved: (AXIS2-62) DeSerializing Envelopes with multiple optimized contents.
Posted by Thilina Gunarathne <cs...@gmail.com>.
Hi all,
Actually this happens when deserializing (A typo in the previous Jira) -
Receving a MTOM optimised message with more then one part.
Even though the bug is resolved just before the .9 release it's not included
in the .9 release. If somebody is having problems in .9 when it comes to
receiving other elements along with Optimized binary elements, then pls try
using a build from the svn checkout.
Regards,
~Thilina
On 7/5/05, Thilina Gunarathne (JIRA) <ji...@apache.org> wrote:
>
> [ http://issues.apache.org/jira/browse/AXIS2-62?page=all ]
>
> Thilina Gunarathne resolved AXIS2-62:
> -------------------------------------
>
> Resolution: Fixed
>
> Altered StAXSoapModelBuilder. When an END_ELEMENT event is return from the
> XMLStAX parser at the point of setting complete (line 327) earlier it casted
> the lastNode to a OMElement., which prevented OMText being a lastNode.
> Changed it so that it'll be casted to a Node.
> OMNode e = (OMNode) lastNode;
> Also altered MTOMStAXSOAPModelBuilder so that it'l not set complete the
> OMText's at the point of creating.
>
>
> > Serilizing Envelopes with multiple optimized contents.
> > ------------------------------------------------------
> >
> > Key: AXIS2-62
> > URL: http://issues.apache.org/jira/browse/AXIS2-62
> > Project: Apache Axis 2.0 (Axis2)
> > Type: Bug
> > Reporter: Thilina Gunarathne
> > Assignee: Thilina Gunarathne
>
> >
> > <my:data>
> > <my:subData>
> > <xop:Include href="cid:2-2846124687180564971@schemas.xmlsoap.org"
> xmlns:xop="http://www.w3.org/2004/08/xop/Include"></xop:Include>
> > </my:subData>
> > <my:subData>
> > <xop:Include href="cid:25194435278458331510@schemas.xmlsoap.org"
> xmlns:xop="http://www.w3.org/2004/08/xop/Include"></xop:Include>
> > </my:subData>
> > </my:data>
> > When handling the above XML MTOMSoapModelBuilder creates the OM tree
> like follows.
> > Element my:data has olny one subData child. Next subData child is lost
> in the OM tree.
>
> --
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of the administrators:
> http://issues.apache.org/jira/secure/Administrators.jspa
> -
> For more information on JIRA, see:
> http://www.atlassian.com/software/jira
>
>
--
"May the SourcE be with u"