[picocontainer-dev] JMX / JNDI and exposing

Hi all, 

It seems to me that current approach to exposing
components to JNDI / JMX is bit of suboptimal. 

Currently JMX/JNDI behaviours would expose component
on getComponentInstance() ( and if they are upstack
from caching, on every getComponentInstance() ) , and
there is also visitors which poke adapters to force
exposition. 

However, biggest problem for those adapters is that 
they need additional data, which is difficult to
provide in scripting environment. 
( JMXExposed requires MBean server, which may be
unavailable  to the moment of script parsing. Not to
speak about passing it to xml / beanshell script in
builder ) 

I would propose to move all the exposing functionality
to visitors. 

Advantages:
 - simplier scripts, no headaches about initial
context
or mbean servers there. 
 - explicit control when something is exposed. 

Disadvantages:
 - need of explicit call to visitor after container
creation ( but it is also current state ) 

regards,
( 


----[ Konstantin Pribluda http://www.pribluda.de ]----------------
JTec quality components: http://www.pribluda.de/projects/


       
____________________________________________________________________________________
Pinpoint customers who are looking for what you sell. 
http://searchmarketing.yahoo.com/

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email