Could you use a filter to parse the language from the path and use that to
create/lookup the appropriate object (Locale?) and put it where JSTL expects
to find it?
Chris
On Apr 1, 2009 6:41 PM, "Casper Bang" <casper_at_jbr.dk> wrote:
I'm happily using the MVC and JSP templating mechanism of Jersey, however I
have a problem as to i18n when this is part of an addressable resource i.e.
/lang/{language}/. Using the formatting library that's part of JSTL isn't an
option, as it relies solely on the language specified in he request header.
I tried a few things thus far but can't find a reliable and scalable
solution. Only thing i can think of now is to write my own tag handler for
some custom tag, but before looking into that I just wanted to hear if the
community has any input. Any ideas much appreciated. :)
/Casper