[ http://issues.apache.org/jira/browse/XALANJ-232?page=all ]
Brian Minchau updated XALANJ-232:
---------------------------------
Version: Latest Development Code
(was: 2.0.x)
> setTransformState not called until after startDocument
> ------------------------------------------------------
>
> Key: XALANJ-232
> URL: http://issues.apache.org/jira/browse/XALANJ-232
> Project: XalanJ2
> Type: Bug
> Components: transformation, Xalan-interpretive
> Versions: Latest Development Code
> Environment: Operating System: All
> Platform: PC
> Reporter: Shane Curcuru
> Assignee: Xalan Developers Mailing List
>
> Either we need to update the javadoc for TransformerClient and
> TransformState,
> or we need to fix the QueuedStartDocument.flush(ResultTreeHandler rth) method
> to
> properly call setTransformState first, before startDocument.
> The seriousness of this bug depends on how much tooling interfaces might want
> to
> do during the startDocument event.
> Also, the flush() method seems to be a little schitzophrenic: at first it
> does:
> m_contentHandler.startDocument();
> but later it calls it's own getContentHandler() before trying to call
> setTransformState().
> Shouldn't we change this method to:
> - always call getContentHandler()
> - do the cast check and setTransformState first, then startDocument, then
> fireGenerateEvent(), and finally super.flush()? Or am I missing something (I
> haven't looked at it deeply)
> TestID: TransformStateAPITest.testCase1
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
