> -----Original Message----- > From: Stefano Mazzocchi [mailto:[EMAIL PROTECTED]] > > In short, instead of a competitive tagline 'use Cocoon instead of J2EE > or .NET' (which would eventually emerge out of a Cocoon Pet > Shop demo), > we should do something different 'no matter what you what to do with > your web, Cocoon will help you doing it better'. [please, excuse the > shitty marketing tone, but we are talking about vapor anyway] > Having de-constructed PetStore ( at least on paper ... ), I would imagine that the proposal was to use Cocoon for managing PetShop GUI and not the entire PetStore application. The J2EE implementation of PetStore GUI implements its own MVC framework to manage the JSPs and is fairly indep. of the backend J2EE application components that use JNDI, JDBC, EJBs, MDBs, and JMS for backend logic implementation.
By replacing the mgmt. of JSPs for GUI by Cocoon, Cocoon community will only demostrate how Cocoon could fit in into a J2EE application and in the process, reduce programming complexity significantly. Ofcourse, the inherent assumption is that it will reduce complexity. /Pankaj. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
