[ 
https://issues.apache.org/jira/browse/XERCESJ-1201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Glavassevich resolved XERCESJ-1201.
-------------------------------------------

    Fix Version/s: 2.10.0
       Resolution: Fixed

The StAX event API implementation has been integrated for quite some time now. 
I ended up completing this work. Lucian, thanks very much for the contribution. 
It will be included in Xerces-J 2.10.0.

> Initial contribution for StAX Event API
> ---------------------------------------
>
>                 Key: XERCESJ-1201
>                 URL: https://issues.apache.org/jira/browse/XERCESJ-1201
>             Project: Xerces2-J
>          Issue Type: New Feature
>          Components: StAX
>    Affects Versions: 2.8.1
>            Reporter: Lucian Holland
>            Assignee: Michael Glavassevich
>             Fix For: 2.10.0
>
>         Attachments: xercesPatch.txt
>
>
> This is my initial contribution for the StAX Event API work I have been 
> doing. It is not yet complete but I am keen to get something into SVN at this 
> stage... Things still outstanding:
>   * DTD parsing
>   * Event Writing is still fairly sketchy and needs work and a lot more 
> testing
>   * One of the reader tests fails because the SAXStreamReader can't expose 
> the whole infoset at the moment
>   * There may not been anything to do, but I haven't even slightly thought 
> about locale/platform issues like character encoding/line-endings yet.
> I have included my changes to build.xml in the patch file; these may or may 
> not be welcome at this stage. Basically these introduce a dependency on an 
> API jar for StAX and an easymock.jar (the version compatible with JDK 1.3). 
> As yet I haven't tried testing the easymock stuff with JDK 1.2, so there may 
> need to be some conditional stuff in the build file (how does one get hold of 
> jdk 1.2 these days? Is anyone actually using 1.2?). I've also added something 
> that runs my initial test suite.
> I've also included a random patch to DOMXMLStreamReaderImpl to fix a 
> character encoding thing in one of the comments that javac kept issuing 
> warnings about.
> I've tried testing on a clean checkout but I have no doubt that I've missed 
> something somewhere and it will all break horribly :-)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to