The following issue has been updated:
Updater: Brian Minchau (mailto:[EMAIL PROTECTED])
Date: Sat, 4 Sep 2004 10:49 AM
Changes:
assignee changed from Xalan Developers Mailing List
description changed from It'd be fairly trivial to change ElemMessage to
pass the user-provided message
as a parameter to the createMessage call, and to enhance
XSLTErrorResources.ER_STYLESHEET_DIRECTED_TERMINATION to include that text
appropriately; this would yield a more useful exception text when the
xsl:message was invoked with terminate="yes".
The improvement wouldn't be picked up in other languages until they rewrote
their internationalization message files to use this additional data, but
wouldn't do any harm; they'd continue to see the old message in the meantime.
We might have to update a few testcases.
Appears worth doing. to It'd be fairly trivial to change ElemMessage to pass the
user-provided message
as a parameter to the createMessage call, and to enhance
XSLTErrorResources.ER_STYLESHEET_DIRECTED_TERMINATION to include that text
appropriately; this would yield a more useful exception text when the
xsl:message was invoked with terminate="yes".
The improvement wouldn't be picked up in other languages until they rewrote
their internationalization message files to use this additional data, but
wouldn't do any harm; they'd continue to see the old message in the meantime.
We might have to update a few testcases.
Appears worth doing.
environment changed from Operating System: All
Platform: All to Operating System: All
Platform: All
priority changed to Blocker
Component changed to Diagnostic messages/resources
Component changed from Xalan-interpretive parser
---------------------------------------------------------------------
For a full history of the issue, see:
http://issues.apache.org/jira/browse/XALANJ-1219?page=history
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/XALANJ-1219
Here is an overview of the issue:
---------------------------------------------------------------------
Key: XALANJ-1219
Summary: Enhance ElemMessage to include message in exception text.
Type: Bug
Status: Unassigned
Priority: Blocker
Project: XalanJ2
Components:
Diagnostic messages/resources
Versions:
CurrentCVS
Assignee:
Reporter: Joe Kesselman
Created: Wed, 9 Oct 2002 1:43 PM
Updated: Sat, 4 Sep 2004 10:49 AM
Environment: Operating System: All
Platform: All
Description:
It'd be fairly trivial to change ElemMessage to pass the user-provided message
as a parameter to the createMessage call, and to enhance
XSLTErrorResources.ER_STYLESHEET_DIRECTED_TERMINATION to include that text
appropriately; this would yield a more useful exception text when the
xsl:message was invoked with terminate="yes".
The improvement wouldn't be picked up in other languages until they rewrote
their internationalization message files to use this additional data, but
wouldn't do any harm; they'd continue to see the old message in the meantime.
We might have to update a few testcases.
Appears worth doing.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
