Hi!
Aaron Mulder wrote:
> across all clients of that locale. I suppose the way to approach this is
> to create separate bean entries in ejb-jar.xml for the same classes with
> one JNDI name per bean per locale and an environment entry naming the
> locale?
That would be possible, yes.
> This is a little irritating since now the client must look up a
> locale-dependent JNDI name. Any other suggestions?
Why does the bean itself have to be locale-dependent? Is it messages
that are being localized, or..? This sounds like a job for the client..
/Rickard
--
Rickard �berg
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
