That sounds more like opinion than fact. EJB's seem to work fine, and do a good job, where they fit.
Why would you say that if you use EJBs you'll have to use .CRAP? On Wed, 2002-02-20 at 11:42, Vic Cekvenich wrote: > Home page of Jakarta has this > http://jakarta.apache.org/site/news.html#0130.2 > on this: > http://www.mail-archive.com/general%40jakarta.apache.org/msg03376.html > > I agree. Doing EJBs is bad on many levels and creates more problems. > Avoid EJB if you want to stay in Java. > > Alternative is to just use Struts + TomCat + RowSet (or DAO if you are > doing something simple or small) and done. This is the sweet spot. MVC > is all you need. > > Alternative, do EJBs and your organization WILL switch to MS .NET on the > > next project, leave J2EE, and you have to learn VB.net. > > EJBs are for newbies. (If you need middleware (very rare) use SOAP) > > lol, > Vic > > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> -- Austin Gonyou Systems Architect, CCNA Coremetrics, Inc. Phone: 512-698-7250 email: [EMAIL PROTECTED] "It is the part of a good shepherd to shear his flock, not to skin it." Latin Proverb -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
