The spec already defines an export policy descriptor that should be used to bind a
handle of the MBean to JNDI. If an MBean has objects it controls and wants them to be
bound to JNDI then it should do this by itself or delegate the task to some other
component that controls the naming service.
Am Son, 2002-03-03 um 12.09 schrieb Juha Lindfors:
The spec already defines an export policy descriptor that should be used to bind a
handle of the MBean to JNDI. If an MBean has objects it controls and wants them to be
bound to JNDI then it should do this by itself or delegate the task to
There's been some discussion of finding things in jndi and in jmx via
obejct name queries, and we currently have quite a few mbeans that end up
binding themselves or an object they control into jndi.
I think we can provide a generic way of dealing with this situation using
the interceptor stack
I think this starting to get too cute as there can be different
semantics as to whether bind or rebind is allowed to overwrite
existing entries, whether missing subcontexts should be created
or represent an error, whether a live reference or a serializable
object should be bound, etc. to me,
