Re: Design Questions about static factory classes
On Sat, 22 May 2010, Rhino wrote:
Tom Anderson <twic@urchin.earth.li> wrote in
news:alpine.DEB.1.10.1005221156210.12091@urchin.earth.li:
For instance, i'm currently on a project which will roll out to 23
countries in the first wave. They're all European and North Amererican,
and in a slightly weird twist, to begin with we're only supporting
english, french, and german as languages. So, if you're a native of the
UK, the US, Canada, France, Switzerland, Luxembourg or a few other
places, you have your own language, but if you live in Hungary or the
Netherlands, you'll have to be able to read english, or in some cases
in eastern Europe, german.
Sorry for the off-topic digression but I just can't help but admit to
some surprise that some eastern Europeans still know German.
Hey, don't look at me. I got the list of locales handed to me from someone
else, and he got it from someone else, and i assume that someone who knew
what they were doing drew it up. Or at least, i hope so; all i can assume
is that someone who had the authority to do it did it.
In the second wave, Korea will be added, and for that, there will be
korean. I assume that in later waves, there will be proper localisation
into national languages, but i haven't heard about that. By that point,
such localisation would not require programmer input (or at least only
a tiny bit) - the client's content management team will be able to add
new locales and their corresponding translations to the system
themselves. We're keeping translations in a database rather than
resource bundle files, so they can do this to a running system without
having to modify the codebase.
What codebase changes concern you? If you do ResourceBundles correctly,
there really aren't any code changes. You simply throw ResourceBundles
for the appropriate languages into the jar and you should be good to go,
right?
And then deploy the JAR and reboot. Not so hot if you're hoping to run a
global ecommerce site.
Do your classes have constructors (or getInstance() methods that
establish a Locale? Do you have setLocale() methods in your classes? If
you don't use either approach, how do you set the Locale and how do you
change it if it needs to be changed?
The system is a web application. We attach a locale to each user session.
We have a component near the top of the servlet container's request
processing chain that looks at the incoming request, and the existing user
object if there is one, and sets the locale accordingly. When a class
needs to know the current locale, it gets hold of the user object for the
current request (via some sort of thread-local variable or some such) and
asks it. So, no class inside the system has any concept of its own locale
- they always use the 'current locale', where that's something that can be
different in different threads that are running at the same time.
tom
--
build the roof with holes in