Hi Sanka, As mentioned here and in the bug, the test fails with the STAX reference implementation (both 1.1.2 and 2.0 final, available from http://stax.codehaus.org/) so I'm just surprised Chinkthaka didn't test this combination. It would be interesting to understand why it fails with the RI as there might be an hidden issue here (either out of spec, or implementation-specific).
Anyhow, switching to Woodstox is fine with me so it's not a blocker by any means. thanks to you both, alex On 7/9/07, Sanka Samaranayake <[EMAIL PROTECTED]> wrote:
Hi Alex, Chinkthaka has verified and closed this issue[1]. Does it sound reasonable or do you wish to reopen it by providing any pointers to recreate it? Thanks, Sanka [1] https://issues.apache.org/jira/browse/WSCOMMONS-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel On 7/9/07, Alex Boisvert <[EMAIL PROTECTED]> wrote: > > On 7/9/07, Sanka Samaranayake <[EMAIL PROTECTED]> wrote: > > > > Further this release version intends to aid the release efforts of > > Axis2 1.3which contains a stax implementation in its distribution > > files. Hence a > > release without fixing this shouldn't matter to them much. > > > Hi Sanka, > > I don't understand what you mean here. If Axis2 1.3 uses StAX, then it > should matter. > > Personally, I don't mind doing the release as-is although I think this is > a > serious problem because it effectively means that you can't use StAX > reliably. In our application that uses Apache ServiceMix and Apache Ode, > we > had to work around the problem by converting everything to DOM. > > Who's most apt for looking into this issue? There is a patch attached to > the issue... can somebody review it? > > cheers, > alex > -- Sanka Samaranayake WSO2 Inc. http://www.bloglines.com/blog/sanka http://www.wso2.org/
