Win a copy of Escape Velocity: Better Metrics for Agile Teams this week in the Agile and Other Processes forum!
  • 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 Pie Elite all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Liutauras Vilda
  • Tim Cooke
  • Paul Clapham
  • Jeanne Boyarsky
  • Ron McLeod
  • Frank Carver
  • Junilu Lacar
Saloon Keepers:
  • Stephan van Hulst
  • Tim Moores
  • Tim Holloway
  • Al Hobbs
  • Carey Brown
  • Piet Souris
  • Frits Walraven
  • fred rosenberger

Caching/using the Handle object

Posts: 3
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I have some doubts concern the Handle object usage and its internal implementation. Is the Handle object thread-safe, I mean, can I cache/use a Stateless Session bean Handle object and use it in a multithread app to retrieve EJBObject references for synchronously?
I am assuming that with Stateful and Entity Beans the handle object will points to a specific EJBObject on the server side. But the handle object on stateless are not linked with any specific EJBObject, therefore it could be possible.
For instance, if I have a Factory class that returns EJBObject based on a previously acquire Handle object. Can this factory use the same Handle object to retrieve several (EJBObject references).
I don't know if its gonna work, I am sure that it will not work concern Statefull and Entity Bean, but it could be possible when using stateless.
I tried to find any specific info on 1.3 spec, but I didn't found any.
Grow a forest with seedballs and this tiny ad:
the value of filler advertising in 2021
    Bookmark Topic Watch Topic
  • New Topic