• 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 all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Bear Bibeault
  • Liutauras Vilda
Sheriffs:
  • Jeanne Boyarsky
  • Tim Cooke
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Jj Roberts
  • Carey Brown
Bartenders:
  • salvin francis
  • Frits Walraven
  • Piet Souris

Home stub class

 
Ranch Hand
Posts: 51
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Why do we need a home stub class on the server? HF Book shows that on page 109?
 
Ranch Hand
Posts: 1683
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Consider a client which does an JNDI lookup on a bean, which returns a Home stub. And for that stub to be returned, the Home object has to be on the server.
The Home stub class would have been generated by the container at deployment time, although the Home stub object might be on a JNDI server at runtime.
[ April 02, 2004: Message edited by: Roger Chung-Wee ]
 
Ranch Hand
Posts: 3178
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
After the client get Home stub from the server, it does not need to JNDI lookup to the server to get a reference to the EJBHome interface... As you see on that page of the HF EJB, the client need to get a reference to the home in order to get connection with the EJBObject to call mehtods on beans...
Hope it helps..
 
reply
    Bookmark Topic Watch Topic
  • New Topic