Just for consistency in the response I guess. Anyway I tried replacing the STaX with SAX and it seems to offer me the consistency I wanted. Raw XMLs are as below.
AXIOM with SAX: <Attribute name="Dummy" type="string">BoB2<sup>TM</sup> is the next generation of wireless modems from iiNet.Here.s why you.ll love him<br /> <ul> <li>Delivers super fast broadband.</Attribute> AXIOM with STaX: <Attribute name="Dummy" type="string">BoB2<sup>TM</sup> is the next generation of wireless modems from iiNet.Here.s why you.ll love him<br /> <ul> <li>Delivers super fast broadband.</Attribute> Regards, Ajit -----Original Message----- From: Andreas Veithen [mailto:[email protected]] Sent: 04 September 2011 16:01 To: [email protected] Subject: Re: AXIOM 1.2.8: Issue with character ">" Why would you want to do that? Andreas On Fri, Sep 2, 2011 at 21:07, Ajit Bhingarkar <[email protected]> wrote: > Ok. Then is there a way to stop my > to get decoded back to ">"? > > -----Original Message----- > From: Andreas Veithen [mailto:[email protected]] > Sent: 03 September 2011 00:33 > To: [email protected] > Subject: Re: AXIOM 1.2.8: Issue with character ">" > > On Fri, Sep 2, 2011 at 20:38, Ajit Bhingarkar <[email protected]> wrote: >> Thanks Andreas. >> >> In my src string "<" and ">" are correctly encoded as "<" and ">" >> respectively. When I create an OMElement out of this input string "<" >> remain as they are while ">" get decoded back to ">". >> >> What I meant by inconsistency is that either both "<" and ">" should >> get decoded to "<" and ">" respectively or ">" should not get decoded >> back to ">". > > Why? Inside element content in a document entity, "<" and "<" have > two different meanings, while ">" and ">" are equivalent and > interchangeable. > >> Regards, >> Ajit >> >> -----Original Message----- >> From: Andreas Veithen [mailto:[email protected]] >> Sent: 02 September 2011 23:55 >> To: [email protected] >> Subject: Re: AXIOM 1.2.8: Issue with character ">" >> >> How is this causing inconsistency? >> >> Andreas >> >> On Fri, Sep 2, 2011 at 07:28, Ajit Bhingarkar <[email protected]> wrote: >>> Hi, >>> >>> >>> >>> We are seeing that when an OMElement is created from a String based XML >>> fragment; > are decided back to ">" while < in the fragment remain. >>> >>> >>> >>> This is causing inconsistency; we would like either > to remain or also >>> < to get decoded as "<". >>> >>> >>> >>> Can you pls share any solution or a workaround? A similar issue is mentioned >>> at http://wso2.org/mailarchive/esb-java-user/2008-August/000728.html. >>> >>> >>> >>> Source -> BoB2<sup>TM</sup> >>> >>> Result -> BoB2<sup>TM</sup> >>> >>> >>> >>> Thanks, >>> >>> Ajit >>> >>> >> >
