Why do we need separate Remote and Local interfaces for EJB 3.0 session beans

jakarta-ee ejb ejb-3.0
Vikas Kedia picture Vikas Kedia · Sep 6, 2009 · Viewed 24.1k times · Source

I was wondering why do we need separate Remote and Local intefaces for EJB 3.0 Session beans. I guess most of the time they would both be defining the same contract. Why cant I have a common interface and in my Bean I should just be able to say that I want this bean to be accessed remotely and/or locally.

thanks Vikas

Answer

rodrigoap picture rodrigoap · Sep 6, 2009

This is what the EJB spec says:

The choice between the local and the remote programming model is a design decision that the Bean Provider makes when developing the enterprise bean.
While it is possible to provide both a remote client view and a local client view for an enterprise bean, more typically only one or the other will be provided.

JSR220 Chapter 3

So when writing a bean think about who is the client, it's very unlikely that a local client will need the same methods or even the same bean that a remote one.

Related questions

EJB: Avoid Transaction rollback

When a (transactional) method of an EJB calls another (transactional) method of another EJB, and an exception is thrown in the second, but catched in the first one, it seems that the transaction is automatically rolled back when the second …

Read More
Consuming local EJB, in the same Container but different ears

I'm triying to consume a Local EJB in the same Glassfish, but different ears. But Glassfish can't found the local EJB or can't consume I read this: According to the JavaEE tutorial, the client of a @Local bean "must run …

Read More
EJB - Lookup failed for 'ejb/BookRequestBean'

I am new to EJB, and was trying "Hello World" type of EJB Java program. Here is my EJB: package dukesbookstore.ejb; @Stateless(name="BookRequestBean", mappedName="ejb/BookRequestBean") @Named public class BookRequestBean { //Other codes here } and here is my client: …

Read More