JavaBeans are pretty much just java objects with get and set methods and a blank constructor. They are accessed only within the scope of the web server. They can be saved in and retrieved from attributes in a given scope, such as the context, session, request, and page. Tomcat supports JavaBeans.
EJB's are objects that require several files for each object to facilitate being shared between two or more computers. Tomcat does not support this at the moment, but JBoss does. JBoss includes Tomcat.
As stated above Tomcat does not support EJBs (some might actually say that this is a major benefit ) and it is unlikely to be extended to support them.
There is another project in the Apache portfolio that is being developed to be an open source EJB platform. For more info see Apache Geronimo Home Page. This is still in a relatively early incarnation but it could become a bit of competition for jBoss.
Andy Bowes<br />SCJP, SCWCD<br />I like deadlines, I love the whoosing noise they make as they go flying past - Douglas Adams
Tomcat at present will not support EJB.EJB's could be run only on a J2EE server (Application server) and Tomcat is not an Application server.
use can use Jboss,which can be downloaded free of cost.The latest version is Jboss 3.2.5.But sun has tested some servers and had given in their site about their performance.Sun one Server plays important role which also free and also tested.
Some servers are not tested by Sun Micro Systems.So dont rely on that.
If you wish to pay and use Bea Weblogic and IBM Websphere etc.. are really good. Thanks With kind regards Satheesh.K
it should not be the question which ejb-container you should use, but maybe the question should be whether to use ejb's at all. You could bypass it all by using hibernate for persistency. A few weeks ago there was a give away on that book and it seemed mighty interesting. Ejb's as we know them are not worth the effort
swimming certificate (A & B), shoelaces diploma, and some useless java ones.