Rickard,
Would the prefix automatically be applied to EJB's? If so my problem with
it, is as follows:
In an ideal world, if you decide to deploy an EJB on a different server
then it used to be on, it should be transparent to the client so the
client really shouldn't have to change how it does its JNDI lookup. A
prefix would require changing the client code whenever you moved an EJB or
maintaining a map of references to real JNDI names which could become very
large.
-Todd
----- Original Message -----
From: "Rickard berg" <[EMAIL PROTECTED]>
To: "jBoss" <[EMAIL PROTECTED]>
Sent: Thursday, November 16, 2000 11:27 PM
Subject: Re: [jBoss-User] Multiple EJB servers
Hey
Here's an idea:
we could add an entry to the jBoss container configuration called "JNDI
prefix". Usually it would be "" (i.e. use localhost with no prefix), but
for cases like this one could set it to for example
"jnp://myhost/myapp/". So, when the container bind the JNDI names it
would use this prefix. That would solve this pretty well I think.
Comments/votes?
/Rickard
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
