You are viewing a plain text version of this content. The canonical link for it is here.
Posted to j-dev@xerces.apache.org by "Lucian Holland (JIRA)" <xe...@xml.apache.org> on 2006/09/29 14:53:50 UTC
[jira] Created: (XERCESJ-1199) SAXXMLStreamReader should attempt to
register a LexicalHandler as well as a ContentHandler
SAXXMLStreamReader should attempt to register a LexicalHandler as well as a ContentHandler
------------------------------------------------------------------------------------------
Key: XERCESJ-1199
URL: http://issues.apache.org/jira/browse/XERCESJ-1199
Project: Xerces2-J
Issue Type: Improvement
Components: StAX
Affects Versions: 2.8.1
Reporter: Lucian Holland
Currently the SAXXMLStreamReader registers the StAXSAXHandler as a ContentHandler on the XMLReader from a supplied SAXSource, but makes no attempt to specify a LexicalHandler. It would be nice if it tried to do this, because that way the SAXXMLStreamReader would get more of the infoset (esp. comments) passed through to it if the underlying XMLReader was capable of doing so...
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org
[jira] Commented: (XERCESJ-1199) SAXXMLStreamReader should attempt
to register a LexicalHandler as well as a ContentHandler
Posted by "Lucian Holland (JIRA)" <xe...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XERCESJ-1199?page=comments#action_12439541 ]
Lucian Holland commented on XERCESJ-1199:
-----------------------------------------
Ah yes, of course. I was testing with woodstox when I wrote that :-)
> SAXXMLStreamReader should attempt to register a LexicalHandler as well as a ContentHandler
> ------------------------------------------------------------------------------------------
>
> Key: XERCESJ-1199
> URL: http://issues.apache.org/jira/browse/XERCESJ-1199
> Project: Xerces2-J
> Issue Type: Improvement
> Components: StAX
> Affects Versions: 2.8.1
> Reporter: Lucian Holland
> Assigned To: Michael Glavassevich
>
> Currently the SAXXMLStreamReader registers the StAXSAXHandler as a ContentHandler on the XMLReader from a supplied SAXSource, but makes no attempt to specify a LexicalHandler. It would be nice if it tried to do this, because that way the SAXXMLStreamReader would get more of the infoset (esp. comments) passed through to it if the underlying XMLReader was capable of doing so...
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org
[jira] Commented: (XERCESJ-1199) SAXXMLStreamReader should attempt
to register a LexicalHandler as well as a ContentHandler
Posted by "Michael Glavassevich (JIRA)" <xe...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XERCESJ-1199?page=comments#action_12439534 ]
Michael Glavassevich commented on XERCESJ-1199:
-----------------------------------------------
I was thinking more along the lines of just producing the internal subset string. The XMLStreamReader needs to pull that together from all of the elementDecl(), attributeDecl(), etc... events. We're not doing that yet.
> SAXXMLStreamReader should attempt to register a LexicalHandler as well as a ContentHandler
> ------------------------------------------------------------------------------------------
>
> Key: XERCESJ-1199
> URL: http://issues.apache.org/jira/browse/XERCESJ-1199
> Project: Xerces2-J
> Issue Type: Improvement
> Components: StAX
> Affects Versions: 2.8.1
> Reporter: Lucian Holland
> Assigned To: Michael Glavassevich
>
> Currently the SAXXMLStreamReader registers the StAXSAXHandler as a ContentHandler on the XMLReader from a supplied SAXSource, but makes no attempt to specify a LexicalHandler. It would be nice if it tried to do this, because that way the SAXXMLStreamReader would get more of the infoset (esp. comments) passed through to it if the underlying XMLReader was capable of doing so...
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org
[jira] Commented: (XERCESJ-1199) SAXXMLStreamReader should attempt
to register a LexicalHandler as well as a ContentHandler
Posted by "Lucian Holland (JIRA)" <xe...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XERCESJ-1199?page=comments#action_12439398 ]
Lucian Holland commented on XERCESJ-1199:
-----------------------------------------
My tests (with a slight tweak) now green bar - excellent! Thanks Michael.
I had been assuming that there wasn't an awful lot of point in the handler worrying about the DTD side of things, given that it only ever exposes the DTD as a single string. I suppose the StaXSAXHandler could process these events, and then the XMLEventReader could check to see if the StreamReader it was backed by supported some special internal interface for getting access to them, otherwise it would fall back to an alternative mechanism; that would probably be more efficient at the cost of some separation of concerns...
> SAXXMLStreamReader should attempt to register a LexicalHandler as well as a ContentHandler
> ------------------------------------------------------------------------------------------
>
> Key: XERCESJ-1199
> URL: http://issues.apache.org/jira/browse/XERCESJ-1199
> Project: Xerces2-J
> Issue Type: Improvement
> Components: StAX
> Affects Versions: 2.8.1
> Reporter: Lucian Holland
> Assigned To: Michael Glavassevich
>
> Currently the SAXXMLStreamReader registers the StAXSAXHandler as a ContentHandler on the XMLReader from a supplied SAXSource, but makes no attempt to specify a LexicalHandler. It would be nice if it tried to do this, because that way the SAXXMLStreamReader would get more of the infoset (esp. comments) passed through to it if the underlying XMLReader was capable of doing so...
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org
[jira] Assigned: (XERCESJ-1199) SAXXMLStreamReader should attempt
to register a LexicalHandler as well as a ContentHandler
Posted by "Michael Glavassevich (JIRA)" <xe...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XERCESJ-1199?page=all ]
Michael Glavassevich reassigned XERCESJ-1199:
---------------------------------------------
Assignee: Michael Glavassevich
> SAXXMLStreamReader should attempt to register a LexicalHandler as well as a ContentHandler
> ------------------------------------------------------------------------------------------
>
> Key: XERCESJ-1199
> URL: http://issues.apache.org/jira/browse/XERCESJ-1199
> Project: Xerces2-J
> Issue Type: Improvement
> Components: StAX
> Affects Versions: 2.8.1
> Reporter: Lucian Holland
> Assigned To: Michael Glavassevich
>
> Currently the SAXXMLStreamReader registers the StAXSAXHandler as a ContentHandler on the XMLReader from a supplied SAXSource, but makes no attempt to specify a LexicalHandler. It would be nice if it tried to do this, because that way the SAXXMLStreamReader would get more of the infoset (esp. comments) passed through to it if the underlying XMLReader was capable of doing so...
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org
[jira] Resolved: (XERCESJ-1199) SAXXMLStreamReader should attempt
to register a LexicalHandler as well as a ContentHandler
Posted by "Michael Glavassevich (JIRA)" <xe...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XERCESJ-1199?page=all ]
Michael Glavassevich resolved XERCESJ-1199.
-------------------------------------------
Resolution: Fixed
The StAXSAXHandler is now set as the LexicalHandler and DeclHandler on the XMLReader. It's now able to handle comments and CDATA sections. It still needs a bit of work to support DTD events (as well as the entity declaration and notation properties).
> SAXXMLStreamReader should attempt to register a LexicalHandler as well as a ContentHandler
> ------------------------------------------------------------------------------------------
>
> Key: XERCESJ-1199
> URL: http://issues.apache.org/jira/browse/XERCESJ-1199
> Project: Xerces2-J
> Issue Type: Improvement
> Components: StAX
> Affects Versions: 2.8.1
> Reporter: Lucian Holland
> Assigned To: Michael Glavassevich
>
> Currently the SAXXMLStreamReader registers the StAXSAXHandler as a ContentHandler on the XMLReader from a supplied SAXSource, but makes no attempt to specify a LexicalHandler. It would be nice if it tried to do this, because that way the SAXXMLStreamReader would get more of the infoset (esp. comments) passed through to it if the underlying XMLReader was capable of doing so...
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org