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)
Thanks for the convincing argument. So tell me how using Struts+Tomcat+RowSet you get: - location independence - distributed processing - failover and clustering support - transactional object behaviour for non-data classes - pooled business objects Ans since you're using SOAP, how do you handle things like massive object creation issues on the SOAP Server? Write all that infrastructure again? Sure why not. -- dIon Gillard, Multitask Consulting http://www.multitask.com.au/developers -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
