• 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 ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Why do we need Entity Bean Local Component Interface ?

 
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi People.

Can any one help me regarding the following issue :

Its never advisable to acess the entity beans remotely. the best performance which we can get it to use
Entity beans locally and provide a remote session bean to acess the local entity bean

Or use the remote session bean to acess the co- located Entity bean.

then why do we have the remote home and compoenet interface for an Entity bean when its never used .


Cheers
Param
 
Ranch Hand
Posts: 8945
Firefox Browser Spring Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

then why do we have the remote home and compoenet interface for an Entity bean when its never used .



Local interfaces were introduced from EJB 2.0. Earlier versions had just the remote interfaces. Remote interfaces are useful when Entiy needed to be accessed from another JVM. Usually you will find entity and session colocated, so remote are not used. This resulted in introduction of local interfaces in EJB 2.0.

Hope this helps.
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic