Hi!
Robert Taylor wrote:
> I think I get the picture now.
> Test app lives in one VM, JBoss lives in another VM.
> Test app creates RMI object (allocates memory address etc...) and binds to
> JNDI.
> Test app exits. Memory address to RMI object has no meaning.
> Test app starts again, finds the RMI stub in JNDI but crashes because stub
> does not reference old RMI object address space.
Exactly.
> I'm not quite clear on what exactly an MBean is except that it refers to JMX
> some how.
You guessed right.
> I'm guessing that it can be used as a sort of start up class that can be
> called when JBoss starts up. This way the RMI object would live in the JBoss
> VM and a call to it would access a valid object reference.
Yup, that is the idea. You can copy an existing MBean in jBoss and go
from there. You can, for example, copy the org.jboss.util.Info(MBean)
classes and modify so that it creates your RMI object instead. Then add
it to jboss.conf (see how Info is added for example) and off you go :-)
/Rickard
--
Rickard �berg
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
