|My understanding is that the purpose of the double indirection is
|to make the
|case where you have many beans and many resources in the the one file more
|manageable.
Yes the reason is that. If you have many beans and one db it becomes very
useful.
Say for example you deploy 120 beans as
Scott M Stark wrote:
Ok, I see some utility in that although a global search/replace is still easier
for my money. It would be easy to allow for direct specification of the
jndi binding under the session/resource-ref element via a jndi-name element
while still allowing for the use of the
We use a double indirection layer to resolve the JNDI name for an ejb-jar/resource-ref
element and I don't see why this can't be handled by a single layer. For example, given
a javax.sql.DataSource reference in an ejb-jar like
ejb-jar
enterprise-beans
session
On Sun, May 06, 2001 at 08:03:42PM -0700, Scott M Stark wrote:
We use a double indirection layer to resolve the JNDI name for an
ejb-jar/resource-ref
element and I don't see why this can't be handled by a single layer. For example,
given
a javax.sql.DataSource reference in an ejb-jar like
