On Jan 24, 2008 2:33 PM, Steve Thompson <[EMAIL PROTECTED]> wrote:
> I have a customer who has requested the ability to view multiple
> locales on a page.  It looks like I can do this fine with Wicket
> through the use of properties files,

Probably combined with overriding getLocale of component for the
pieces of content that should be rendered in a different locale than
the session's.

> but what I would like to do is
> automatically detect which locales there are properties files for.  Is
> this possible, and if so, how?

We don't have a facility for that. Scanning which files exist
relatively to a class is not difficult, but the problem is what you
miss with a component might exist higher up the hierarchy. Also, when
a search would take the regular search hierarchy into account, it
would include custom components, which sometimes ship with more/
different languages than your application supports.

So... I think basing the available locales on which properties (and
xml, we support those too) files are packaged with your components is
not a good idea, unless a scan just directly relative to one component
suffices. Are you sure the available locales isn't application-wide
for your app?

Eelco

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to