DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21540>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21540 [PATCH] XPath messages now sent to XPATHMessages class Summary: [PATCH] XPath messages now sent to XPATHMessages class Product: XalanJ2 Version: CurrentCVS Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: Other Component: org.apache.xpath AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] This patch relieves the "double duty" that org.apache.xalan.res.XSLMessages has had in printing messages/warnings in both the Xalan and XPATH levels. It configures XPATH-based messages to use the org.apache.xpath.res.XPATHMessages class created earlier this year by the Xalan team. (Required about 100 function call search & replaces in about 30 files; all changes included in this patch.) So instead of: XSLMessages.createXPATHMessage(...., ...); There is now: XPATHMessages.createMessage(....., ....); in the XPATH.* packages. Other changes included in the patch: 1) Because it's no longer handling xpath messages, xalan.res.XSLMessages now derives directly from xml.res.XMLMessages instead of xpath.res.XPATHMessages. 2) XPATHMessages.createXPATHMessage() was simplified to XPATHMessages.createMessage() (same as XSLMessages.createMessage() is currently.) 3) The function XPATHMessages.createXPATHMsg(XPATHBundle, msgKey, args)--is identical to the base class XMLMessages.createMsg(XPATHBundle, msgKey, args), so the former was removed and its lone call in XPATHMessages replaced by the latter (as currently done by XSLMessages). Compiles and tests fine with the sample XSLT files. Glen
