• 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
  • Ron McLeod
  • Tim Cooke
  • Liutauras Vilda
  • Jeanne Boyarsky
Sheriffs:
  • Paul Clapham
  • Rob Spoor
  • Junilu Lacar
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Piet Souris
  • Carey Brown
Bartenders:

EJBObject's KPA

 
Ranch Hand
Posts: 75
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello,

Head First EJB page 87....
EJBObject's only job is to capture the incoming client calls to the bean.

Who is responsible for deserializing the arguments and providing the real heap based objects to the real bean class?


If container services are kicking in then the argument objects should already be available so as to include them in transaction and other services.

Can anyone provide the list of Key Performance Area's (KPA's) for EJBObject?

Thanks
Chetan
 
Ranch Hand
Posts: 379
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Chetan Sahasrabudhe:
Hello,

Head First EJB page 87....
EJBObject's only job is to capture the incoming client calls to the bean.

Who is responsible for deserializing the arguments and providing the real heap based objects to the real bean class?


If container services are kicking in then the argument objects should already be available so as to include them in transaction and other services.

Can anyone provide the list of Key Performance Area's (KPA's) for EJBObject?

Thanks
Chetan



EJB uses RMI as underlying network architecture, therefore it's the container, through RMI, which takes care of remote communication. EJBObject, which is one of the classes the Container creates, implementing the bean remote component interface, acts as a middleware between the client and the real bean. Let's think at the following example: in an EJB container there is only one law: nothing can arrive to the bean if the container (or one of its 007) intercepted it first.

The lifetime is: client -> serialization -> server -> deserialization -> Container (EJBHome/EJBObject, low level services) -> bean. An EJBObject is the way a container can assure its services, still ensuring the bean-based functionalities. To see the KPA of a container (which include EJBObject features), just have a look at the EJB[Local]Object, EJB[Local]Home, SessionContext, EntityContext, UserTransaction interfaces and the services that those offer to the client. To those, add CMP for entity beans, asynchronous communication between clients and beans, the API guaranteed by each EJB 2.0 compliant server.
 
Chetan Sahasrabudhe
Ranch Hand
Posts: 75
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello Marco,

Thanks for the KPA, as you know I am still in range of 80 - 150 pages of headfirst ejb, some of the things make sense to me, but some still sound, ummm .. Puzzling.

I guess I will take it forward from here and will get back to KPA's after a while.

Thanks for the pointers
Regards
Chetan
reply
    Bookmark Topic Watch Topic
  • New Topic