• 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
  • Liutauras Vilda
  • Bear Bibeault
  • Jeanne Boyarsky
  • Tim Cooke
Sheriffs:
  • Knute Snortum
  • Junilu Lacar
  • Devaka Cooray
Saloon Keepers:
  • Ganesh Patekar
  • Tim Moores
  • Carey Brown
  • Stephan van Hulst
  • salvin francis
Bartenders:
  • Ron McLeod
  • Frits Walraven
  • Pete Letkeman

EJB Home Factory  RSS feed

 
Ranch Hand
Posts: 174
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I plan to implement EJB Home Factory but this involves caching oh EJB Home.
Can anyone tell me whether JBOSS and JONAS allows stale homes ?
 
Bartender
Posts: 19807
93
Android Eclipse IDE Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Yes. It's common practice to cache the Home interface in order to avoid the JNDI overhead, and, in fact, I'm preparing to publish something that does just that.
The downside is that if you hot-redeploy the EJB, the home interface reference will go stale unless you add logic to detect and correct that.
 
Arijit Ghosh
Ranch Hand
Posts: 174
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks Tim. But I need something urgently... I am using Jboss. I have edited the necessary web.xml and ejb-jar.xml file.

Now the main thing ---
to write the EJBHome Factory Java file ....
Any pointers ?
 
Tim Holloway
Bartender
Posts: 19807
93
Android Eclipse IDE Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The way I do it is just to create a servlet that runs at server startup. In that servlet's init() method, I lookup the home interface(s) and store them into the application context.
 
sharp shooter, and author
Ranch Hand
Posts: 1913
6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Take a look at Floyd's EJB Design Patterns book on http://www.theserverside.com.
The way that I've done it is simply to have a singleton class through which you can lookup and cache JNDI references. Using a singleton does mean that you may have more than one copy in a cluster, but it does mean that you can use the factory from the presentation (web) and business (ejb) tiers of your architecture.
Simon
 
It is sorta covered in the JavaRanch Style Guide.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!