Answer Posted / guest

The EJB 2.0 public draft specification includes requirements
on EJB container/server providers which enable
interoperability for invocations on enterprise beans. These
requirements enable communication with J2EE clients
including JavaServer Pages, Servlets, Application Clients as
well as with enterprise beans in other EJB containers. The
goal of these features is to allow enterprise bean
invocations to work even when client components and
enterprise beans are deployed in J2EE products from
different vendors. Support for interoperability between
components includes transaction propagation, naming services
and security services.


The interoperability mechanisms in EJB 2.0 are based on the
IIOP protocol from the Object Management Group. The
extensions supporting distributed transaction propagation,
security (using SSL) and naming service access are all based
on OMG standards. J2EE container products may also use
vendor-specific protocols in addition to IIOP.

Name the acid properties of a transaction.

1048

---

Can beans who are involved in transaction have 'passivation' process?

972

---

What is a local interface?

1128

---

What do you understand by session facade?

985

---

The ejb container implements the ejbhome and ejbobject classes. For every request from a unique client, does the container create a separate instance of the generated ejbhome and ejbobject classes?

989

---

How entity beans support container managed persistence?

2430

---

What is ejb role in j2ee?

1102

---

What is the difference between ejbcreate() and ejbpostcreate?

935

---

Enlist the changes in EJB 2.1 ?

1017

---

Define Initial Context?

1002

---

What is @resource in java?

985

---

What is bean-managed transaction?

1088

---

What is the difference between message driven beans and stateless session beans?

976

---

What is enterprise bean?

972

---

How to import ejb project in eclipse?

1045

---