Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Align tribes.util.StringManager implementation with tomcat.util.Strin…
…gManager implementation. git-svn-id: https://svn.apache.org/repos/asf/tomcat/trunk@1680783 13f79535-47bb-0310-9956-ffa450edef68
- Loading branch information
Keiichi Fujino
committed
May 21, 2015
1 parent
ee4fffb
commit 548d604
Showing
1 changed file
with
132 additions
and
32 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
548d604
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why we should maintain three StringManager in catalina.tribes.util, naming and tomcat.util.res, or why we need special StringManager for catalina.tribes and naming?
548d604
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The patch is unnecessary. The Tribes StringManager does not have to support multiple locales whereas the main StringManager (o.a.t.u.res) does.
There are multiple StringManager implementations to avoid unwanted dependencies.