Hello,
Earlier this year Ramesh Mandava ([EMAIL PROTECTED]) contributed
changes to Xalan-J Interpretive so that it would use classes that extend
ListResourceBundle to represent its messages rather than using properties
files.
Currently, XSLTC (Xalan-J Compiled) uses classes that extend the
abstract ResourceBundle class to do the same thing; it uses named constant
integers as indices into the arrays of error messages defined by those
classes. That scheme seems a little fragile, so for consistency with the
interpretive processor, I went through and changed the XSLTC
ResourceBundles to ListResourceBundles; Gordon Chiu ([EMAIL PROTECTED])
made the changes necessary to retrieve the messages using string keys
instead of integer array indices.
All these changes are pending on my computer, but I wanted to provide
anyone who feels that the XSLTC messages should remain as ResourceBundles
rather than ListResourceBundles with the opportunity to object.
Thanks,
Henry
------------------------------------------------------------------
Henry Zongaro Xalan development
IBM SWS Toronto Lab Tie Line 969-6044; Phone (905) 413-6044
mailto:[EMAIL PROTECTED]
