> In short
> > 1- where are get/set container called on plugins, when? ( I
> miss it in init
> > right now)
>
> They're called in Container.init(), EntityContainer.init() and
> StatelessSessionContainer.init().
>
> (Although, now that you got my attention to it, some plugins have been
> missed. The cache isn't initialized for example. Will fix)
right
>
> > 2- whether you call or not, why the BeanClassLoader for root
> naming only...
>
> What else do you want there?
well my point is remove it since...
> > 3- Isnt' the "bean" in Container a better class to put all
> metaData instead
> > of passing information implicitely.
>
> What "bean" are you referring to? The "metaData" attribute? Well, that
> *is* where the metadata is..
all your information should be there.
> > 4- Since your interceptors are "newed" for container
> interceptors at this
> > point you should use the set, and then 3 applies
Well setting the container on all those interceptor mean that they are not
shared just belong to one... that is something we might "reverse". It makes
sense... bean should be the only place unless you can justify the
"necessity" for BeanCLassLoader JNDI root as opposed to just using the bean
metadata... if you ask me it is because you use your EJX stuff and you don't
have a "storeRoot" ;-) never mind.
marc
>
> Not quite with you here. Can you expand this point.
>
> /Rickard
>
> --
> Rickard �berg
>
> @home: +46 13 177937
> Email: [EMAIL PROTECTED]
> http://www.telkel.com
> http://www.jboss.org
> http://www.dreambean.com
>
>
