This week's book giveaway is in the Java 8 forum.
We're giving away four copies of Java 8 in Action and have Raoul-Gabriel Urma, Mario Fusco, and Alan Mycroft on-line!
See this thread for details.
The moose likes EJB and other Java EE Technologies and the fly likes EJB Local Home interface look up in RAD with WebSphere 5.0 test environment. Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Java 8 in Action this week in the Java 8 forum!
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "EJB Local Home interface look up in RAD with WebSphere 5.0 test environment." Watch "EJB Local Home interface look up in RAD with WebSphere 5.0 test environment." New topic
Author

EJB Local Home interface look up in RAD with WebSphere 5.0 test environment.

Kiran Nallagonda
Greenhorn

Joined: Jun 27, 2006
Posts: 1
Hi,
I have RAD 6.0. I'm installing one application with stateless and stateful session beans. I have local home interfaces for each of the beans.
I can deply them without any errors. I can test them with UTC. In UTC interface it is showing local home interfaces in local EJB beans folder. When I use that JNDI name to look up the Local home interface, it giving me home interface instead of localhome interface and hence the classcastexception. Do you anybody had same problem with RAD and local home interfaces?
Please let me know.
Thanks,
Kiran.
Vladimir Manolov
Greenhorn

Joined: Jun 28, 2006
Posts: 5
Hi,

I think you get remote home objects after the lookup since the universal test client is a different application and is not part of your ear (where your application is). You can only use local interfaces within the boundaries of one ear (one application). To me this sounds doesn't sound like a RAD problem. Try accessing the local home interface through some bean in the same application. Just make yourself some dummy bean that makes the lookup and check what kind of interface you get. I hope this helps.

Cheers,
Vladimir M.
Jeanne Boyarsky
internet detective
Marshal

Joined: May 26, 2003
Posts: 29287
    
140

Kiran,
If it works in the UTC (as it should), but not in the JNDI lookup, something is wrong with the JNDI string. Are you using the format:
"local:ejb/ejb/com/..." ?

If you don't have the "local:" part, WebSphere assumes you want the remote interface.


[Blog] [JavaRanch FAQ] [How To Ask Questions The Smart Way] [Book Promos]
Blogging on Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, OCAJP, OCPJP beta, TOGAF part 1 and part 2
Jeanne Boyarsky
internet detective
Marshal

Joined: May 26, 2003
Posts: 29287
    
140

And welcome to JavaRanch!
Randy Schnier
Greenhorn

Joined: Aug 01, 2006
Posts: 2
Don't ever use the local: context from application code. The local: context is a hidden, internal implementation aspect of WAS and it may change or be eliminated at any time. The only supported mechanism for looking up local EJB homes in WAS is to create an ejb-local-ref and ejb-link in the calling component, point the ejb-link at the target EJB, and look up the local home in the java:comp/env namespace at whatever name was assigned to the ejb-local-ref.

Randy Schnier
IBM WebSphere

Originally posted by Jeanne Boyarsky:
Kiran,
If it works in the UTC (as it should), but not in the JNDI lookup, something is wrong with the JNDI string. Are you using the format:
"local:ejb/ejb/com/..." ?

If you don't have the "local:" part, WebSphere assumes you want the remote interface.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: EJB Local Home interface look up in RAD with WebSphere 5.0 test environment.
 
Similar Threads
Problem looking up local interface of Session Beans - WSAD 5.1, WAS 5.0 Test Env
EJBLocalHome
doubt
local JNDI lookup
EJB 2.0, WSAD 5, example problem