• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Devaka Cooray
  • Knute Snortum
  • Paul Clapham
  • Tim Cooke
Sheriffs:
  • Liutauras Vilda
  • Jeanne Boyarsky
  • Bear Bibeault
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Ron McLeod
  • Piet Souris
  • Frits Walraven
Bartenders:
  • Ganesh Patekar
  • Tim Holloway
  • salvin francis

Adding JNDI functionality to vanilla IBM JDK 1.3.0  RSS feed

 
Ranch Hand
Posts: 72
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

Is there anyway of enabling a vanilla IBM JDK 1.3.0 to use JNDI?

My issue is that I need to act as an EJB client (iiop), but without access to a WAS installation / jar files.

Basically, its a WMQI (2.1.6) thing. We've successfully managed to get a WMQI java node to act as a EJB client but only using a WebSphere installation.

I don't need WebSphere jars to use the EJB, only to access the naming service

I'm looking at using Sun's JNDI implementation.. though possibly by-passing JNDI and just using rmi/iiop/corba is an option I've yet to explore.

Has anyone any experience of this?

Thanks

James
 
james render
Ranch Hand
Posts: 72
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Yeah, stupid question. The 1_3_0 JDK ships with JNDI functionality.
 
Consider Paul's rocket mass heater.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!