Strange problem.. I use the connection pooling on Websphere 4.05 (Windows) and everything is fine BUT when I deploy the app on WAS on Solaris I get a naming exception. The code to access the datasource is as follows: ---------------------------------------- instance.parms.put(Context.INITIAL_CONTEXT_FACTORY,com.ibm.websphere.naming.WsnInitialContextFactory.class.getName()); javax.naming.Context ctx = new InitialContext(parms); javax.sql.DataSource ds = (javax.sql.DataSource)ctx.lookup("jdbc/superman"); con = ds.getConnection(); return con; ------- in the WAS admin console, both the jdbc driver and the datasource have the name 'superman'. Also is there a way to test the datasource from the admin console (I know that 4.0 AE has that ability) Thanks - PJ
really did not get ur question.. if u need to test the datasource from the admin console... u go to the datasource.. and where the properties are displayed, there is a button to test the datasource. Is this the test u are referring to? or are u referring to some other test on teh datasource?
Best Regards,<br />Nagendra Prasad.
Proudly marching to the beat of a different kettle of fish... while reading this tiny ad
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop