> A full global JNDI-name would be "<app-name>/<ejb-name>" (e.g.
> "mycompany/myapp/MyBean"). app-name is jBoss specific and given in
> deployment information, whereas ejb-name is given in standard
> ejb-jar.xml.
Sebastien essentially pitched this to me when he was in the metadata stuff.
I need to make sure it is kosher, right now I think it is.
One other real benefit is that we go closer to the "application EAR" as
basic metadata repository (naming, classloaders, also as MBean?) and that in
my mind is a superior design than the curent metadata attached to the
container.
Now before you go ape-shit again :), it is not a defect of the architecture
;-) that was done in the same way in jboss1.0 we really had no notion of
what an EAR was. But now we do and the container copies of the metadata are
sort of weak... we can do better based on the application. (btw Tomcat
integration would then work from this CL metadata, somehow).
marc
>
> > Now, before you go ape-shit,
>
> That's a new one I have never heard before.. funny.. :-)
>
> Makes sense now?
>
> /Rickard
>
> --
> Rickard �berg
>
> Email: [EMAIL PROTECTED]
> http://www.telkel.com
> http://www.jboss.org
> http://www.dreambean.com
>
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
>
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
