OK, that's true. Your VM will crash if the JNI code crashes, I'll grant you that. However, you could deploy your EJB's that indirectly call the JNI in a separate application server from other code (you can run > 1 application server on a node).
But anyway, that's probably a dead horse. I think you've misread the Custom Services documentation it says that in the custom services you can't invoke JNDI but that's
in the context of this application server. If your Custom Service code starts another process, then that other process should be able to access JNDI like normal. The key here is that the JNDI server itself runs in one of two places
(a) in 4.0 AE the JNDI Server runs in the admin process, which is outside of any Application server
(b) in 4.0 AEs the JNDI Server run in the context of the application server process.
What it comes down do is making sure that JNDI is up before you register your RMI server. That can be as simple as a busy loop in your RMI process. If it fails to obtain an initial context, wait a few seconds, then try again.
BTW, one more change -- I think I misspoke when I said you can registre JRMP objects -- you really do have to use RMI over IIOP -- but that's just using the -IIOP parameter on the rmic.
Kyle
------------------
Kyle Brown,
Author of
Enterprise Java (tm) Programming with IBM Websphere See my homepage at
http://members.aol.com/kgb1001001 for other WebSphere information.