• 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 ...
  • Campbell Ritchie
  • Bear Bibeault
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
  • Tim Cooke
  • Liutauras Vilda
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • fred rosenberger
  • salvin francis
  • Piet Souris
  • Frits Walraven
  • Carey Brown


Ranch Hand
Posts: 37
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
HFEJB page: 252 qestion 5.
If the client calls a bean that has been removed how come the container could throw either of these.
- Walk Rustin
Posts: 23
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Walk Rustin
Hi Walker,
the client calls a method from it's remote component object which translates to an rmi call to the "bodyguard" on the container's server. So, the scenerio is either the client has called remove() but later on still uses the ref to the remote component object or the container removes the comp object, and the client has no way of knowing this until he calls on it remotely.
NoSuchObjectException inherits from RemoteException. My guess is NoSuchObjectException is much more informative but that which exception you actually get is container implementation specific.
Hope I didn't confuse things even more.
Ranch Hand
Posts: 1066
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Also both happen to be rmi exceptions, a part of the JDK and not the javax.ejb package.
This looks like a job for .... legal tender! It says so right in this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
    Bookmark Topic Watch Topic
  • New Topic