Hi!
marc fleury wrote:
>
> Ok so I see that AbstractInterceptors do define get and set container.
>
> and if this is there then I must advise against the "BeanClassLoader" since
> the container.getMetaData is there.
No, it's not. The BeanClassLoader only holds the root of the java:
namespace.
> 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)
> 2- whether you call or not, why the BeanClassLoader for root naming only...
What else do you want there?
> 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..
> 4- Since your interceptors are "newed" for container interceptors at this
> point you should use the set, and then 3 applies
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
