JNDI is only used to look up the default bundle name if the localize tag
does not provide one - and the only reason I used JNDI was that it seems to
be the only way to access environment variables in the web application
descriptor. (which I think is a problem in the servlet spec) But
theoretically since you're using JNDI to access a local web app descriptor,
it's not going to go remote anyway. (I'm not a JNDI expert though - someone
else who is please feel free to weigh in)
That said, default bundle names still don't work for Tomcat 3.2. I'm all
for putting it somewhere that works for all environments, its just that I
figured the web app descriptor was the best place to provide a default.
If we dropped the web app descriptor environment var approach and stored the
bundle name in an application scoped variable, how would you recommend we
make sure it gets set before the first page is hit?
Tim
-----Original Message-----
From: Wong Kok Wai [mailto:[EMAIL PROTECTED]]
Sent: Friday, March 02, 2001 9:20 AM
To: [EMAIL PROTECTED]
Subject: Re: i18n taglib submission (was RE: internationalization tags)
Looking thru' the sources, I've one question: why is JNDI used to look up a
resource bundle? It is expensive if the JNDI is a remote service. Why not
just
use an application scoped singleton?
Tim Dawson wrote:
> With some assistance I've finally completed the packaging of the i18n lib
> and am ready to submit it to the group.
>
> It can be dropped into the jakarta-taglibs folder and built. The only
catch
> is that you have to define a LOG4J_JAR environment variable.
>
> Tim Dawson
> Chief Software Architect
> WAM!NET, Inc.
>
