Answer / ch.n.v.ganesh

First, relationships are maintained through foreign
keys, but you do not define foreign keys as conventional
EJB variables; they are generated and maintained by the
container.

Second, relationships generate additional methods on the
local interfaces of the EJBs involved. Consequently, you
will need to work with the Home interfaces for beans
through JNDI, rather than using factory classes as you
might for accessing them through their Remote
interfaces.

Finally, Container Managed Relationship (cmr) fields
may be used in EJB QL queries, just like conventional
fields, but only for EJBs within the same jar file.

Life cycle methods in stateful session beans?

1 Answers   CTS, iFlex,

---

How Client will contact the Bean?

3 Answers   Four soft, Tech Mahindra,

---

can u explain about design patterns like singleton,builder,factory

0 Answers   EdgeSoft,

---

What are the benefits of ejb?

0 Answers  

---

What is software architecture of ejb?

0 Answers  

---

What’s new in the ejb 2.0 specification?

0 Answers  

---

What is session bean in ejb?

0 Answers  

---

How can I call one EJB from inside of another EJB?

2 Answers   CTS,

---

Basic types of Enterprise JavaBeans?

4 Answers   TCS,

---

How stateful session beans will maintain consistency, across transaction updates?

2 Answers  

---

Can remove() be a Stateless Session bean?

0 Answers  

---

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

0 Answers  

---