Hi,
I just want to confirm something w.r.t. EJB 3.0.
I can create, read, update and delete EJB entities without a need for application server. This is because this part of the J5EE framework is javax.persistence part which can run standalone, i.e. no need for app server.
However, EJB Sessions do require an App server, because they require a JNDI lookup.
Have I got this correct?
Apologies if this is a stupid question.
Not a stupid question at all.The JNDI lookup isn't really the issue. From a spec perspective only a full Java EE platform implementation can implement the core EJB 3.0 functionality. Unlike the Java Persistence API, the core EJB functionality is not permitted to be shipped as a stand-alone product. The main reason is that the ejb programming model is built on top of many other important server-side services such as transactions, security, remote IIOP and webservice access, connector 1.5 integration, etc.If you remove all these services you defeat much of the purpose of using EJB in the first place.
--ken
