Increased Duke Dollars for an old thread without reply

Question

Hi All,
Wonder anyone experienced a similar problem and solved it.
I have a stand-alone application that talks to EJBs. It has been running well either from another machine or the same machine with WebSphere server for WebSphere 3.5. After we upgrade to WebSphere 4.0. I can still run it from another machine with properties: (tmx-huri is the machine hosting WebSphere)
providerURL=iiop://tmx-huri:900/
ctxFactory=com.ibm.websphere.naming.WsnInitialContextFactory
and add the following jar files into the classpath from WebSphere 4.0: ejs.jar (this is from 3.5 because 4.0 does not have it), websphere.jar, ns.jar, util.jar, ras.jar, ujc.jar.
But if I copy all the same files to tmx-huri itself and just change providerURL to:
providerURL=iiop://localhost:900/
It will show message saying 'Cannot instantiate class: com.ibm.websphere.naming.WsnInitialContextFactory'
If I use
ctxFactory=com.ibm.ejs.ns.jndi.CNInitialContextFactory
instead, it always throughs NamingException saying cannot find the bean.
I appreciate any comment and suggestions.
PC
The basic code is shown here:
Properties namingProps = new Properties();
namingProps.put(javax.naming.Context.PROVIDER_URL, providerURL);
namingProps.put(javax.naming.Context.INITIAL_CONTEXT_FACTORY,initialContextFactory);
// Create an Initial Context.
try {
initContext = new InitialContext(namingProps);
catch (javax.naming.NamingException e) {
System.err.println ("EJBHomeFactory:constructor() Could not retrieve initial context - all EJB lookups will fail. Exception: "+e.getMessage());
where providerURL and initialContextFactory can be retrieved from a property file.
To lookup EJB:
Object home = initContext.lookup(beanName);

Answer 1

An interesting situation. I use to work with WAS 3.5 ages ago (2 years?) and remember coding stuff as you have done with the properties for the initial context factory. I then went and played with Oracle 9iAS for a while and am back with WebSphere for the last 6 months or so in WAS 4. I had forgotten how I use to do things in 3.5 and the way we are doing stuff here in version 4, is simply
Context entityContext = new InitialContext(System.getProperties());
Object obj = entityContext.lookup("java:comp/env/ejb/myBean"); Then we do the narrow.... blah blah blah.
The point being that we are not worrying about copying any jars from anywhere. We are unit testing inside Websphere Studio Application Developer, and then deploying into WAS V4 and it all just goes.
Maybe give that a try and let the websphere environment provide you its defaults.
Cheers,
Peter.