Actions
Bug #4457
closedMessageListener.message() terminate parameter set incorrectly
Start date:
2020-02-10
Due date:
% Done:
100%
Estimated time:
Legacy ID:
Applies to branch:
9.9, trunk
Fix Committed on Branch:
9.9, trunk
Fixed in Maintenance Release:
Platforms:
Description
(Since 9.9.1.6) A call to a user-supplied MessageListener.message()
method does not set the terminate parameter to true when <xsl:message terminate="yes">
was specified.
Unit test TestMessageListener.testMessageTerminate()
created.
Updated by Michael Kay over 4 years ago
- Status changed from New to Resolved
- Fix Committed on Branch 9.9, trunk added
A slightly messy fix, but it works: the xsl:message code now inserts into the pipeline (between the document builder and the message emitter) a custom ProxyReceiver
that adds the TERMINATE property to the startDocument()
event.
Updated by O'Neil Delpratt over 4 years ago
- Status changed from Resolved to Closed
- % Done changed from 0 to 100
- Fixed in Maintenance Release 9.9.1.7 added
Patch applied in the 9.9.1.7 maintenance release.
Please register to edit this issue
Actions