|
From: Rod J. <rod...@in...> - 2003-05-19 15:32:00
|
All,
You may have seen the recent changes making JndiServices (formerly static)
an object called JndiTemplate. This is consistent with other templates, and
much better for testing. (Statics are the enemy of unit testing.)
Although you won't have noticed unless you've tried to do anything fancy
with JNDI, this means that a number of classes now expose JndiTemplate bean
properties. The default is new InitialContext() behaviour, as you'd expect.
However, it's now possible to use separate JNDI environments for different
beans: e.g. EJB proxies that access different remote servers.
I've made this easier to configure by adding a JndiTemplate property editor.
Thus you should be able to do this for any bean that uses a JndiTemplate:
<property name="jndiTemplate">
myJndiEnvironmentProperty1=whatever
allTheStandardOrVendorSpecificKeys=values
</property>
Rregards,
Rod
|