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 resource-name indirection if desired.
The content model would change from:
<!ELEMENT resource-ref (res-ref-name , resource-name)>
to
<!ELEMENT resource-ref (res-ref-name , (resource-name | jndi-name | res-url))>
>
> 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.
>
> <res-ref-name> describes what the resource *does*
> <resource-name> describes what the resource is *called*
> <res-jndi-name> describes where the resource is *located*
>
> During development all of your resource might be located in the one DBMS, e.g.
> HSQL or something. In production you might choose to separate the inventory
> database to an external Oracle instance, but leave the product and accounts
> databases running somewhere else.
>
> I agree that the double indirection causes a lot of confusion. Perhaps we can
> make it optional?
>
> Toby.
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-development
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
