This week's book giveaway is in the Servlets forum.
We're giving away four copies of Murach's Java Servlets and JSP and have Joel Murach on-line!
See this thread for details.
The moose likes EJB and other Java EE Technologies and the fly likes naming.Context.PROVIDER_URL Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Murach's Java Servlets and JSP this week in the Servlets forum!
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "naming.Context.PROVIDER_URL" Watch "naming.Context.PROVIDER_URL" New topic
Author

naming.Context.PROVIDER_URL

Jason Kim
Greenhorn

Joined: Apr 13, 2003
Posts: 17
Hi.
I am a newbie in J2EE using WebSphere V5.
While migrating an EJB application from WebSphere V3.5 to WebSphere V5, I came across "javax.naming.Context.PROVIDER_URL".
In WebSphere V3.5, it seems that it is used to resolve JNDI name for EJB or to locate home interface of the EJB.
Am I correct ?
However, in WebSphere V5, it causes an NamingException and the application only works without it.
So can I just leave it out and safely assume that
WebSphere V5 doesn't require "javax.naming.Context.PROVIDER_URL" ?
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: naming.Context.PROVIDER_URL
 
Similar Threads
naming.Context.PROVIDER_URL
WebSphere Technology for Developers (J2EE 1.3)
problem in use:forward WAS
Specifying number of pooled EJB instances ..Urgent.!
WSAD V4 - How do I set my JDK level for JAVAC compiles?