Cocoon and EJB are addressing different problem spaces. Cocoon is fairly specifically aimed at content delivery systems -- Web sites, intranets, sites that basically need to present information from a variety of sources in a variety of formats. Cocoon is an XML transformation and presentation system. Cocoon does not specifically address issues such as database persistence, inter-server communication, or (yet) application deployment.
EJB engines are addressed at application developers -- developers working on complex applications (web-based or otherwise) involving extensive database development and complex logic. The focus with EJBs is on what happens *inside* the server. You wouldn't want to develop an airline reservation system with (just) Cocoon. You wouldn't want to develop a website and documentation production environment with (just) EJBs. I look forward to the two becoming more closely interoperable. Having an XSP framework which can work with an EJB environment would be a good start.... Cheers! Rob At 08:08 PM 4/1/2002 -0800, Steven Punte wrote: >Dear Cocoon User Group: > > OK. Cocoon and the EJB world cannot be compared >side- > by-side since they are different beasts, but I put > EJB in the subject because it represents the "J2EE > Flag Ship;" at least, that is my perception. > > A better subject line could have been "Cocoon vs. > JSP + ServerBeans + EJB" or similar. > > Never-the-less, I've been studying the hell out of > EJB technology for the past two months, and EJB is > suppose to be good stuff? > > Cases in point: > > o One is suppose to write four, may six files > for each EJB: XxxBean, XxxHome, XxxRemote, > ejb-jar.xml, and now maybe XxxLocalHome and > XxxLocalRemote (isn't that last one an > oxymoron?). > > o Adding another process space between the > servlet container and the database is a > good thing? I don't care how much object > pooling goes on. The fastest software is > software that doesn't exist. > > o Entity EJB beans can provide caching, but > haven't databases been providing caching for > the last two decades already? > > o Ya, CMP EJB are nice, but plain old JDBC does > most of this anyway WITHOUT any subclassing. > > o Transactions? Doesn't look that difficult with > JTA, but I haven't done a project yet with JTA. > > o Distributed EJB's for improved reliability? Wow, > there is sure a lot to potentially go wrong > here. > > In summary: > > 1) For the complexity, has anyone found that the EJB > technology really brings good stuff to the table? > > If so, are such projects mainstream, or somewhat > corner case like the super high rel banking domain? > > > 2) It seems like for nearly all projects, Cocoon >makes > a much functionality and productivity richer > starting base than what Sun is advocating. > > But I'm probably preaching to the quire here. > > > Inquiring Minds Want To Know: > > Steven P. Punte > > >Steven P. Punte >Candlelight Software >By Candlelight If Necessary! >[EMAIL PROTECTED] >http://www.candlelightsoftware.com > >__________________________________________________ >Do You Yahoo!? >Yahoo! Tax Center - online filing with TurboTax >http://http://taxes.yahoo.com/ > >--------------------------------------------------------------------- >Please check that your question has not already been answered in the >FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> > >To unsubscribe, e-mail: <[EMAIL PROTECTED]> >For additional commands, e-mail: <[EMAIL PROTECTED]> --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
