Why not only one interface for a EJB ??

From: Amardeep Verma (addverma_at_email.com)
Date: 11/24/03 

Date: 24 Nov 2003 06:09:07 -0800

Hi,
    As you know there are two interfaces, home and component interface
to a EJB Bean. But why are there two interfaces? Why not have only one
interface which will do the work of both? What is the advantage of two
interfaces?

Anybody can shed light on this topic??

Thanking you in Advance
Have a nice day

Relevant Pages

  • Re: Why not only one interface for a EJB ??
    ... > As you know there are two interfaces, home and component interface ... > to a EJB Bean. ... But why are there two interfaces? ... map to class methods. ...
    (comp.lang.java.programmer)
  • Why not only one interface for a EJB ??
    ... As you know there are two interfaces, home and component interface ... to a EJB Bean. ... Thanking you in Advance ...
    (comp.lang.java)
  • Why not only one interface for a EJB ??
    ... As you know there are two interfaces, home and component interface ... to a EJB Bean. ... Thanking you in Advance ...
    (comp.lang.java.programmer)
  • Re: Why not only one interface for a EJB ??
    ... > to a EJB Bean. ... But why are there two interfaces? ... It's like the factory pattern I guess. ... It simply seperates the Bean instance/interface and its ...
    (comp.lang.java)
  • Re: Why not only one interface for a EJB ??
    ... > to a EJB Bean. ... But why are there two interfaces? ... It's like the factory pattern I guess. ... It simply seperates the Bean instance/interface and its ...
    (comp.lang.java.developer)