[
https://issues.apache.org/jira/browse/XALANJ-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17804579#comment-17804579
]
Joe Kesselman commented on XALANJ-2720:
---------------------------------------
Many thanks, I'll take a look. If we need to revert it and look for a better
solution, we can certainly do so.
--
/_ Joe Kesselman (he/him/his)
-/ _) My Alexa skill for New Music/New Sounds fans:
/ https://www.amazon.com/dp/B09WJ3H657/
Caveat: Opinionated old geezer with overcompensated writer's block. May be
redundant, verbose, prolix, sesquipedalian, didactic, officious, or redundant.
> tranform function in TransformerIdentityImpl resetting content handler
> ----------------------------------------------------------------------
>
> Key: XALANJ-2720
> URL: https://issues.apache.org/jira/browse/XALANJ-2720
> Project: XalanJ2
> Issue Type: Bug
> Security Level: No security risk; visible to anyone(Ordinary problems in
> Xalan projects. Anybody can view the issue.)
> Components: SAX
> Reporter: Abhijeet Singh
> Assignee: Gary D. Gregory
> Priority: Critical
> Attachments: TestTransformer.java
>
>
> In the commit:
> [https://github.com/apache/xalan-java/commit/b03ee965878f7cc62d4ae8a8d9dd0a28acf01fab]
> changes were made to reset the content handler to the old content handler
> after doing the parse operation while earlier the ContentHandler was set to
> TransformerIdentityImpl permanently in the tranform(Source, Result) function,
> this is because the setting old content handler is being done in the finally
> block.
> I am getting a null pointer exception for content handler now as it was
> automatically set to Tansformer IdentityImpl.
> Is this intended behaviour? If not please provide a new release with the fix.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional commands, e-mail: dev-h...@xalan.apache.org
