> I eventually resorted to deploying all my global scope shared
> objects in a separate jar which is deployed on the server, not the ejb
> app, ie. I put it in /orion/lib/thing.jar. Make sure that any references
> to such objects are nulled before passivation or the ejb's won't serialize
> cleanly...
> Note also that this scheme will allow you to have a "server" scoped
object.
But I do NOT want server scoped objects. I have several applications running
in the same server (several instances of the same code base), and each
application needs its own set of objects.
I guess I have to use JNDI.
