InitialContext from server-side applications

Question

Just a question to see if what I am doing is correct.
According to this link:
http://www.weblogic.com/docs51/classdocs/API_ejb/EJB_design.html#1031811
if you are an internal client of an ejb you should use
Context ctx = new InitialContext();
instead of having to specify all the parameters like
Properties h = new Properties();
h.put(Context.INITIAL_CONTEXT_FACTORY,
"weblogic.jndi.WLInitialContextFactory");
h.put(Context.PROVIDER_URL, url);
h.put(Context.SECURITY_PRINCIPAL, user);
h.put(Context.SECURITY_CREDENTIALS, password);
Context ctx = new InitialContext(h);
I am trying to connect to a connection pool from within an ejb. This
ejb is running in the weblogic server and the connection pool is in the
same server and is restricted to use by a special account that we
setup. If I just get the context by calling new InitialContext() and
then get the dataSource through this context, I won't have access rights
to the connection pool. So what I did was to provide everything but the
provider_url to get the context. Example:
Properties h = new Properties();
h.put(Context.INITIAL_CONTEXT_FACTORY,
"weblogic.jndi.WLInitialContextFactory");
h.put(Context.SECURITY_PRINCIPAL, user);
h.put(Context.SECURITY_CREDENTIALS, password);
Context ctx = new InitialContext(h);
This way I provide everything but the URL to the weblogic server. The
reason I do this is because we have multiple weblogic servers and since
we don't want it to tied to only one server, I leave out the url and
assume that the InitialContext() will be gotten from the local server,
basically whichever server it is running on. It seems to work fine
right now. My concern is if the way I am explaining things is correct
and if what I am doing sounds logical.
Any input on this would be appreciated.

Answer 1

If you do not specify the properties, it defaults to the user guest. This
is a simplification that is useful if you have users logging in through
servlets/JSP.
Thanks,
Michael
Michael Girdley
BEA Systems Inc
"Senthil Kumar S" <[email protected]> wrote in message
news:[email protected]...
There is no restriction that u should not populate properties to get
initialContext.
U are doing the right way.
bhavin patel wrote:
Just a question to see if what I am doing is correct.
According to this link:
http://www.weblogic.com/docs51/classdocs/API_ejb/EJB_design.html#1031811
if you are an internal client of an ejb you should use
Context ctx = new InitialContext();
instead of having to specify all the parameters like
Properties h = new Properties();
h.put(Context.INITIAL_CONTEXT_FACTORY,
"weblogic.jndi.WLInitialContextFactory");
h.put(Context.PROVIDER_URL, url);
h.put(Context.SECURITY_PRINCIPAL, user);
h.put(Context.SECURITY_CREDENTIALS, password);
Context ctx = new InitialContext(h);
I am trying to connect to a connection pool from within an ejb. This
ejb is running in the weblogic server and the connection pool is in the
same server and is restricted to use by a special account that we
setup. If I just get the context by calling new InitialContext() and
then get the dataSource through this context, I won't have access rights
to the connection pool. So what I did was to provide everything but the
provider_url to get the context. Example:
Properties h = new Properties();
h.put(Context.INITIAL_CONTEXT_FACTORY,
"weblogic.jndi.WLInitialContextFactory");
h.put(Context.SECURITY_PRINCIPAL, user);
h.put(Context.SECURITY_CREDENTIALS, password);
Context ctx = new InitialContext(h);
This way I provide everything but the URL to the weblogic server. The
reason I do this is because we have multiple weblogic servers and since
we don't want it to tied to only one server, I leave out the url and
assume that the InitialContext() will be gotten from the local server,
basically whichever server it is running on. It seems to work fine
right now. My concern is if the way I am explaining things is correct
and if what I am doing sounds logical.
Any input on this would be appreciated.