|
Home > Archive > WebSphere Application Server > May 2005 > the age old client jndi - any different for was 6?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
the age old client jndi - any different for was 6?
|
|
|
| Hi,
we are running websphere 6.0.0.1.
We do continuous integration - junit tests run as part of an automated build.
Some of these junit tests may invoke remote ejbs to kick off some integration tests.
In previous versions of was, it was very difficult to get an external client and jndi working with was (tricks included using a big list of was jars, with the ibm jdk, and potentially using the initial context factory (java.naming.factory.initial) com.sun
.jndi.cosnaming.CNCtxFactory
Has this situation gotten any easier with websphere 6?
Is there a simple way (i.e. a short list of jars and an initial context factory) to access jndi from a client?
I haven't fully investigated the application client route as I feel this is overkill for what I need.
tia,
Hugh Madden
| |
| Paul Ilechko 2005-05-18, 6:05 pm |
| me@hughmadden.com wrote:
> I haven't fully investigated the application client route as I feel
> this is overkill for what I need.
It's a lot easier than figuring out which jars you need. Installing the
client gives you all the right jars. However, the following link is a
good summary of the options available to you:
http://publib.boulder.ibm.com/infoc...appclients.html
|
|
|
|
|