At 15:44 16/07/2002 +0200, you wrote: >Berin Loritsch wrote: > >>Cocoon can definitely use its own blueprint. A Cocoon Application >>Blueprint is an essential document that we need. There are two ways >>of using Cocoon: integrated in with a traditional J2EE environment, >>and standalone. The blueprint will define exactly what part of the >>puzzle Cocoon supports. It will also define which patterns work well, >>why they work well, and the antipatterns which suck all your time. > >Quite some people and companies I know are currently building Cocoon-based >CMS and webpublishing apps, often charging considerable amounts for this >kind of 'product'. Wyona of course serves as some kind of reference >example (while they do so in open source, which is good). > >But if you look at the basic use cases of a webbased CMS, those also cover >general functions as authentication, form-based editing, some workflow, >session management etc etc... > >I agree webshopping fits in most people's head as some blueprint >application, but integrating what we've got (Cocoon, Slide, Lucene, forms >processing, authentication and (portal) publishing building a CMS could >also become an aggregation of best practices, IMHO.
Take away Slide (for the moment) and that's exactly what I'm doing in my current project. Just a statement to back up Steven's. - I'm having a member section on the site that uses a mySQL databse for user authentication - I'm using the portal as a CMS/logisitc tool with an XML file for user authentication - I have a form based menu.xml editor for menu editing - I have a page editor from sourceforge, sadly enough using LGPL, to edit the content of the pages - I index the content using Lucene - the logistical functions are to be created but there are enough form processing things in cocoon to do this - I'm using esql to dynamically generate forms with and from database content. Add, delete, update and record navigation is provided. Still need to add pagination. - I will generate PDF documents to be used in mail merge applications - I will use the sendMail logicsheet to do e-mailings - lots of smaller stuff This is a real life application that is easy to maintain, scalable and very performing. The code is a bit of a mess right now due to several tests that are still in there, but after cleanup I'm going to make it available in OSS (apart from the editor which will remain LGPL of course). Voices are rising in our company to set up a true document(ation) management system for all the projects we are doing. Some of those are really big and have lots of stuff. I'm trying to push Forrest, and thus Cocoon, to get this done. This application will use all of the stuff Steven mentioned. it will even use SVG to generate graphs and images for personalized documents. Cocoon is a big bag of goodies. We got to put them together to create a candy factory. Bert ></Steven> >-- >Steven Noels http://outerthought.org/ >Outerthought - Open Source, Java & XML Competence Support Center >[EMAIL PROTECTED] [EMAIL PROTECTED] > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, email: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
