What do you think about rename class LocalizedBundle to AbstractEntry?
Woody
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
final enhancements
Index: LocalizedText.java
===
RCS file:
/home/cvspublic/jakarta-commons-sandbox/i18n/src/java/org/apache/commons/i18
n/LocalizedText.java,v
retrieving revision 1.1
diff -u -r1.1 LocalizedText.java
---
final enhacements
Index: LocalizedError.java
===
RCS file:
/home/cvspublic/jakarta-commons-sandbox/i18n/src/java/org/apache/commons/i18
n/LocalizedError.java,v
retrieving revision 1.1
diff -u -r1.1 LocalizedError.java
---
final enhancements
Index: LocalizedException.java
===
RCS file:
/home/cvspublic/jakarta-commons-sandbox/i18n/src/java/org/apache/commons/i18
n/LocalizedException.java,v
retrieving revision 1.1
diff -u -r1.1 LocalizedException.java
---
Well, once MessageManager (and everything inside) is static we can have only
one manager to all aplications running on vm. What you think to do when we
need one diferent manager, by example, to supply another application ? I
dono what messages id this application will have but if there is some id
What do you think about rename class LocalizedBundle to LocalizedEntry?
I think this is a better name ...
Woody
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]