aspose file tools*
The moose likes Websphere and the fly likes InitialContext creation WAS 5.0 Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » Websphere
Bookmark "InitialContext creation WAS 5.0" Watch "InitialContext creation WAS 5.0" New topic
Author

InitialContext creation WAS 5.0

Gunther Verhemeldonck
Greenhorn

Joined: Jan 21, 2004
Posts: 13
I deployed an application and when I tried to look up one of the session beans, it failed to construct an InitialContext object using the default contstructor. When I specify the factory and url, everything works.

I don't want to specify host specific things! What will happen when I enable clustering? I loose transparency! What is the diffence between the 2 approaches? I just want to use the default constructor !!
Anybody any ideas?
thanx in advance ...


SCJP, SCJD, SCWCD
Kyle Brown
author
Ranch Hand

Joined: Aug 10, 2001
Posts: 3892
    
    5
Do you mean a standalone Java application that's an EJB client, or a Web application? If it's a standalone Java application, the issue is one of which client container you use. Do a search in the InfoCenter for "launchClient.bat" and read up on the J2EE client container.
Kyle


Kyle Brown, Author of Persistence in the Enterprise and Enterprise Java Programming with IBM Websphere, 2nd Edition
See my homepage at http://www.kyle-brown.com/ for other WebSphere information.
Gunther Verhemeldonck
Greenhorn

Joined: Jan 21, 2004
Posts: 13
Ah ok, I get it.
I don't run in a client container. I just lookup the bean in a main()-method.
I'll try to package the client so that it does.
Any hints?
Kyle Brown
author
Ranch Hand

Joined: Aug 10, 2001
Posts: 3892
    
    5
Lots of them in the EJB client development chapter in my book (below).
Kyle
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: InitialContext creation WAS 5.0