"bill.burke(a)jboss.com" wrote :
| That's nice for basic beans, but as I showed before, it is just not so simple for
Java EE land where the ENC -> Global JNDI binding cannot be determine by the available
metadata. To put it in other terms, the available metadata may not be enough to construct
a Kernel identity or exact JNDI binding. The referenced component will need to be
searched for based on the position of the component in the deployment and based on the
little of metadata that was made available by the application developer.
The rules for completing the metadata need to be a pluggable aspect of the deployment
layer so that when deployment processing is complete, the enc deployer and runtime aspect
have nothing to do but create the context and install the correct one. A merge of the
org.jboss.ejb.EjbUtil link resolution and whatever new rules have been added should be the
starting point.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3972339#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...