|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.
Yes, the indirection should be the "generic" case with overwriting if a jndi
name is there.
|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))>
Yes, good call, we are admin friendly for 1 bean and for 100 beans. The 100
beans idea came from Sebastien Alborini BTW, and I thought it was brilliant.
I should have caught the 1 bean case.
marc
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
