Win a copy of Five Lines of Code this week in the OO, Patterns, UML and Refactoring forum!

Sen nathan

Greenhorn
+ Follow
since Mar 27, 2005
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Sen nathan

MDB doesn't have any clients, so it is not possible for a MDB to run in an caller's tranction context.Transaction attribute 'supports' says that either a bean can run in caller's transaction or unspecified transaction context.Hence declaring the 'supports' transaction attribute for MDB doesn't make any sense.
With the Remote clients,you are actually working on the stub, not with the real object.If you use the reflection API for remote clients then you are interrogating the stub not the real object(EJB instance).So you need to use an EJBMetaData object to interrogate about the remote object.

With local clients both the client and EJB instance are in the same heap, so you will be actually working with EJBInstance not with 'remote object'.
Hence the need of an EJBMetaData object is not required.Hope this clarifies you.Letme know if you need further clarification.Cheers...
I understand that the stateless session bean instance creation is not tied to any specific client.But I have a doubt here, Let's say, the container precreates the instances by running constructor,context and ejbCreate.
When it completes the ejbCreate method there won't be any EJBobject as the client wouldn't have invoked the create method in home interface.In that case, how it is possible to get a reference to EJBobject from ejbCreate method.Both in spec as well as in Certification book, it is mentioned that EJBobject reference can be retrieved thru context API from ejbCreate method.