[ http://issues.apache.org/jira/browse/XALANJ-1891?page=all ]

Brian Minchau updated XALANJ-1891:
----------------------------------

    Fix Version: 2.7

> Xalan's Serailizer should have its own message file.
> ----------------------------------------------------
>
>          Key: XALANJ-1891
>          URL: http://issues.apache.org/jira/browse/XALANJ-1891
>      Project: XalanJ2
>         Type: Improvement
>   Components: Serialization
>     Versions: CurrentCVS
>  Environment: Operating System: Other
> Platform: Other
>     Reporter: Brian Minchau
>     Priority: Minor
>      Fix For: 2.7
>  Attachments: org.apache.xml.serizlier.utils.jar, 
> patch.to.java-src.directory.txt, patch.to.java.directory.txt, 
> patch.to.test.directory.txt
>
> 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() ).

-- 
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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to