I've been reading up on EJBs (3.x) and believe I understand the basics. This question is a call for confirmation that I have interpreted the Java EE docs correctly and that I understand these fundamental concepts:An EJB is to an App Container as a Web App (WAR) is to a Web ContainerJust like you deploy a WAR to a Web Container, and that container manages your WAR's life cycle, you deploy an EJB to an App Container, and the container manages your EJB's life cycleWhen the App Container fires up and deploys an EJB, it is given a unique identifier and URL that can be used by JNDI to look up the EJB from another tier (like the web tier)So, when your web app wants to invoke one of your EJB's methods, it looks the EJB up using some kind of service locator (JNDI) and invoke the method that wayAm I on-track or way off-base here? Please correct me & clarify for me if any of these are incorrect. Thanks in advance!
EJB Lifecycle and Relation to WARs
java;web applications;java ee;middleware
You're essentially correct, note that with EJB 3.1, you can have light-weight EJBS that run in your web (servlet) container. Also the JNDI lookup can now be defined as a standard global lookup, so if you migrate to another app server your code doesn't have to change.