[jira] Updated: (XERCESJ-1253) Prototype for SoC2007 project "Add support for the StAX (JSR-173) cursor API to Xerces-J"

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

Wei Duan updated XERCESJ-1253:
------------------------------

    Attachment: StAX_06_03_07.zip

> Prototype for SoC2007 project "Add support for the StAX (JSR-173) cursor API 
> to Xerces-J"
> -----------------------------------------------------------------------------------------
>
>                 Key: XERCESJ-1253
>                 URL: https://issues.apache.org/jira/browse/XERCESJ-1253
>             Project: Xerces2-J
>          Issue Type: New Feature
>          Components: StAX
>            Reporter: Wei Duan
>         Attachments: StAX_06_03_07.zip
>
>
> This code zip is prototype for SoC 2007 project "Add support for the StAX 
> (JSR-173) cursor API to Xerces-J". The code description is as follows.
> Work underway in Xerces on an implementation of JAXP 1.4. The largest 
> technical change in this new edition of JAXP is the addition of StAX 
> (JSR-173) which introduces XML pull parsing APIs to the Java platform. In 
> constrast to push parsing APIs like SAX, StAX gives control back to the 
> application at each step in the parsing process. The goal of this project is 
> to design and implement the cursor-based XMLStreamReader (and filtering 
> support). It should be possible to accomplish this using XNI by building the  
> XMLStreamReader on top of an XMLPullParserConfiguration.
> The prototype validates the technical mechanism which builds stax parser 
> based on XNI and implements intital XNI-based XMLStreamReader. The work done 
> in the prototype also includes:
>    * Use XMLPullConfiguration to simulate stax parsing process.
>    * Implement element, attribute, text, namespacecontext, location methods.  
> 　
> The ongoing work includes:
>    * Support filter function.
>    * Implement DTD, entity referrence, namespace, etc.
>    * Solve the problme that XNI parsing steps do not exactly match the StAX 
> steps. E.g., XNI will treat startDocument xmlDecl as two events, but StAX 
> will treat as one  integrated startDocument event.

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