I think there may be a bug because here's my jndi.properties. I'm pretty
sure there isn't another jndi.properties in my path.
jndi.properties:
java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
#java.naming.provider.url=localhost
java.naming.factory.url.pkgs=org.jboss.naming
I'll look into this more later on. Any insight in the meantime would be
helpful.
Thanks,
Bill
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Scott
M Stark
Sent: Wednesday, April 18, 2001 8:20 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] why is Home lookup an RMI call?
As long as you don't have a Context.PROVIDER_URL set in the env
passed to InitialContext or jndi.properties the Context returned is the
RMI implementation object and calls on it should not involve RMI
invocations.
----- Original Message -----
From: Bill Burke
To: Jboss-Development@Lists. Sourceforge. Net
Sent: Wednesday, April 18, 2001 4:12 PM
Subject: [JBoss-dev] why is Home lookup an RMI call?
All,
(If this is a jboss-user question, I apologize.) I've been doing some
performance testing on my code, and I noticed that Home
lookups on the InitialContext is always an RMI call through jnp even though
the Naming service is in the same VM. Maybe this is a
configuration problem on my part? If not, then is there any reason the
lookup is an RMI call? I know I'm being a little lazy not
researching this myself, just thought maybe somebody has a quick answer.
Also, if this is worth fixing I can probably go in there
and fix it myself.
BTW, I'm using a snapshot of JBoss somewhere between 2.1 and 2.2.
Thanks,
Bill
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
