DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=29651>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=29651 Xalan's Serailizer should have its own message file. Summary: Xalan's Serailizer should have its own message file. Product: XalanJ2 Version: CurrentCVS Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: org.apache.xml.serializer AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Currently the serializer's messages are mixed with Xalan-J interpretives XML messages. The serializer should have its own message file. Also the separation of messages from Java methods that create the messages is not quite what it should be. A new class like org.apache.xml.utils.Messages should be created to handle the creation of messages, which any part of Xalan-J or XSLTC could use. Currently there is a bit too much cut/paste of the message services. Also a message file should have only messages and essentially no methods (except for getContents() ). --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
