Please attach a sample to the Jira report which provokes the exception when run. It's really hard to diagnose bug reports without one.
-- /_ 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. ________________________________ From: Shivani Karol via j-users <j-users@xalan.apache.org> Sent: Wednesday, December 20, 2023 7:42:22 AM To: j-users@xalan.apache.org <j-users@xalan.apache.org> Subject: Query regarding tranform function in TransformerIdentityImpl resetting content handler Hi, 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. Bug is raised too - XALANJ-2720<https://issues.apache.org/jira/browse/XALANJ-2720> Awaiting your inputs. Thanks Shivani Karol 9968283306
