Hi, Unless you're writing an app that really is partitioned into separate web and business tiers on separate machines, then I would recommend using just a servlet engine (tomcat or jetty) plus Spring.
EJB application servers really add to development hassles, due to the need to build jars to deploy stuff into them. Spring (particularly v2.5, recently released) can do most of what an EJB server does if needed but is much more developer-friendly IMO. Note that Spring probably can also handle separated business/web tiers. And because Spring is explicitly all about NOT intruding into the app classes, it does not "lock you in" if the app needs to be scaled up to an EJB appserver later. When writing JSF apps, I can strongly recommend using Spring's JSF integration for managed bean handling, regardless of whether you use an EJB appserver or just a servlet-engine. The "managed bean" facility of JSF1.1/1.2 is really primitive. Using Spring for your managed bean declarations is almost transparent and *much* nicer. Hopefully JSF2.0 will have a better managed bean (IOC) system defined. Or that they will drop that part of the spec completely, and just recommend that an external one be used. Regards, Simon ---- Oscar Duque <[EMAIL PROTECTED]> schrieb: > > Greetings Developers, > > I'm beginning a new MyFaces project, what Application Server do you recommend > for the Deploy, Apache Tomcat or Apache Geronimo ? > > The best choice for the new projects it's Geronimo ? yes, not, Why ? > > Is Geronimo enough mature in order to we can trust our projects to it ? > > Thanks in advance, Oscar Duque > _________________________________________________________________ > Explore the seven wonders of the world > http://search.msn.com/results.aspx?q=7+wonders+world&mkt=en-US&form=QBRE
