Discussions

EJB design: Remote EJBObject for stateless session beans

Bookmark and Share Get thread feed

  1. Remote EJBObject for stateless session beans (4 messages)

    Hi,
    My question is regarding stateless session beans only. The application should be deployed on any application server, so I’m trying to stick to the SPEC.

    I’m using delegate pattern to access EJBs, in the constructor I call service locator to get the home interface and save it as private field in the delegate class. Each business method creates the remote interface home.create() and invoke the business method.
    1. Can I save the remote interface as private field in the class instead of the home? in the constructor I will call service locator and directly create the remote object. in this case I don’t need to create the remote object each method invocation.
    I think this should not be problem since we talk about stateless beans and the fact that same home create same remote interface each create invocation (according to EJB 2 spec).
    And this should not defeat pooling cause the application server pools the bean instances and not the EJBObjects
    2. If section 1 is correct, is it good idea to cache remote interfaces in service locator?
    3. I'm working with local interface too (EJBLocalObject) is the same as interface or it needs special treatment?

    Thanks in advance
    Reply to this

    Threaded Messages (4)

  2. Remote EJBObject for stateless session beans[ Go to top ]

    You can always cache ur remote interface instead of home interface and it doesnt make differece with local interface.
    Hi,My question is regarding stateless session beans only. The application should be deployed on any application server, so I’m trying to stick to the SPEC.I’m using delegate pattern to access EJBs, in the constructor I call service locator to get the home interface and save it as private field in the delegate class. Each business method creates the remote interface home.create() and invoke the business method.1. Can I save the remote interface as private field in the class instead of the home? in the constructor I will call service locator and directly create the remote object. in this case I don’t need to create the remote object each method invocation.I think this should not be problem since we talk about stateless beans and the fact that same home create same remote interface each create invocation (according to EJB 2 spec).And this should not defeat pooling cause the application server pools the bean instances and not the EJBObjects2. If section 1 is correct, is it good idea to cache remote interfaces in service locator?3. I'm working with local interface too (EJBLocalObject) is the same as interface or it needs special treatment?Thanks in advance
    Reply to this Reply to original

  3. Remote EJBObject for stateless session beans[ Go to top ]

    Hi!

    From what I can see, this should work as long as you have stateless beans. At least that's my interpretation of section 7.5.8 in the EJB 2.1 specification. (I am referring to the "Proposed Final Draft" since that is the one I have on the disk now, but I don´t expect such a basic thing to change in such late stage of the specification writing.)

    /Tomas
    Reply to this Reply to original

  4. Remote EJBObject for stateless session beans[ Go to top ]

    Thank you guys for your replies, I still have one open issue. According to the spec EJB 2.0 final release section 6.9.2:
    "All session objects of the same stateless session bean within the same home have the same object identity, which is assigned by the container. If a stateless session bean is deployed multiple times (each deployment results in the creation of a distinct home), session objects from different homes will have a different identity."

    FooHome fooHome = ...; // obtain home of a stateless session bean
    Foo foo1 = fooHome.create();
    Foo foo2 = fooHome.create();
    if (foo1.isIdentical(foo1)) {// this test returns true
    ...
    }
    if (foo1.isIdentical(foo2)) {// this test returns true
    ...
    }

    Does that mean that we have same instance, or doest it access same bean instance?
    what will happened if I cache the remote interface and two different threads invokes its methods in the same time? doest they use different bean instance or they may access the same one (which will lead to throwing exception by application server)

    Thanks
    Reply to this Reply to original

  5. Remote EJBObject for stateless session beans[ Go to top ]

    Does that mean that we have same instance, or doest it access same bean instance?

     For stateless beans, the actual bean is associated only during business method call. So on doing isIdentical(), there are no real comparisons of 2 stateless session beans. But, the client can assume that it is comparing 2 EJBObject instances (although the Container can implement it in any fashion). For Stateless it would be just comparing their EJBHome.

    what will happened if I cache the remote interface and two different threads invokes its methods in the same time? doest they use different bean instance or they may access the same one (which will lead to throwing exception by application server)

    It should lead to throwing java.rmi.RemoteException ( if remote) or javax.ejb.EJBException (if local). A session object is intended to support only a single client. ( Pg 101 - EJB Spec).
    Reply to this Reply to original