Help coderanch get a
new server
by contributing to the fundraiser
  • 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 Pie Elite all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
  • Mikalai Zaikin

Pluggable Application Client restrictions

Posts: 10336
Hibernate Eclipse IDE Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
This is a WAS 6 question. Pluggable Application Clients seems to be the way IBM suggest you should write a traditional stand-alone client application that accesses resources deployed in the WebSphere container, specifically EJBs. There seems to be a restriction that JNDI lookup cannot use JNDI names in the way I'd expect; for example in a client I might want to lookup "java:/comp/env/ejb/MyBean", but if I were running the client against WAS I'd have to lookup "server/ejb/MyBean". Is there any way round this, other than coding the client to be server aware?

Also, does anyone know how to write/run a pluggable client that is runnable on Solaris and Windows?
Listen. That's my theme music. That's how I know I'm a super hero. That, and this tiny ad told me:
We need your help - Coderanch server fundraiser
    Bookmark Topic Watch Topic
  • New Topic