J2EE Localization with WAS
- From: "zets" <zohar.etzioni@xxxxxxxxx>
- Date: 17 Jul 2006 01:50:05 -0700
Hi,
I have a question about localization, and the standard way of doing it
in J2EE, more specifically in WAS6.0. I would like the client to
receive localized messages. One way of doing it, is have the client and
the server in sync with some message catalog, and the client shall
localize the message by an id sent from the server. Another approach is
to add to all API calls in the server, the client locale, and the
server will localize the message. A third approach is to pass the
locale as part of the login process, have the server maintain it, and
localize the messages to the client. The advantage of the last two
approaches is that the client does not need to synchronize its message
catalog with the server. The downside of the last one is that will not
work if the client changes its locale in runtime. The downside of
adding locale to API is that it does not seem reasonable to pollute the
business logic API with localization information.
So, I would go with the last approach of passing the locale in the
authentication, and save it somewhere in the server, only I'm not sure
it's feasible, and less sure that it is the *right* thing.
Help much appreciated!
Thanks.
.
- Prev by Date: Which Swing Component is this?
- Next by Date: problem with TreeMap - element removal fails.
- Previous by thread: Which Swing Component is this?
- Next by thread: problem with TreeMap - element removal fails.
- Index(es):
Relevant Pages
|
