Win a copy of Learn Spring Security (video course) this week in the Spring forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Libraries required for JNDI look by a pure Java Application Client

 
vicky kumar
Ranch Hand
Posts: 55
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Kyle,
I have 2 questions for you:
1) Is Websphere Thin Client the only solution to access remote EJB using JNDI ? If yes, does that not defeat the very purpose of JNDI objects by not enabling to be accessed without thin client.
2) If there is any way to access EJB by a pure Java Application, what/where are the libraries to put in the classpath. Also let me know the properties to initialise the context with (Apart from HOST and Class Name).
Also, any other prerequisite.
We have tried enough so far to access through Java Application (NOT EJB Client) as this application resides in different machine remotely. All efforts in vain so far.
IBM technical support suggests THIN client. What are your comments and suggestions.
Any quick reply will be greatly appreciated.
 
Kyle Brown
author
Ranch Hand
Posts: 3892
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
This is very clearly described both in my book and in the InfoCenter. Yes, the only way to access EJBs in WebSphere is through the thin client, the pluggable client or the application container (e.g. launchClient.bat).
And this doesn't defeat the purpose of EJBs or JNDI -- EJB's WERE NEVER a part of J2SE, which is all you have before you add on the additional libraries. All the thin client is is a large set of libraries. Likewise, the J2EE application container (J2EE client) is just a set of libraries and a batch file to set up your classpath.
I really don't see what the problem is... what's your real concern?
Kyle
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic