"[EMAIL PROTECTED]" wrote : Generically it is a callback interface like
MBeanRegistration
| for services that want to know about their container and their configuration
|
|
| | public interface ContainerRegistration
| | {
| | void setContainer(Container container);
| | void setMetaData(MetaData metaData);
| | }
| |
I would generalize it a tad further, following the per invocation EJB context model we
have in EJB containers:
| public interface ContainerRegisration
| {
| void setInvocationContext(Context ctx);
| }
|
where we give, per invocation, access to the component to the metadata via an
invocation API, this gives the same per invocation granularity we have today in EJBs
for caller principal metadata, for example (for per container, or VM or cluster
metadata you just keep passing the same metadata references for all invocations, this
should not cause additional overhead).
My .02
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3831159#3831159
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3831159
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
