Hello, > ----- Original Message ----- > From: "Stefano Mazzocchi" <[EMAIL PROTECTED]> > Christoph Henrici wrote: > > > > I have been studying, testing and playing around with cocoon in the > > last few days as a newcomer : i am greatly impressed with what ease with > > cocoon "pipelines" arbrary data sources can be "chained" to a result > > target: a very powerful paradigm (pipe) applied in a powerful context > > (http) by using great technology (xml, xlst). > > Yep, I think you really hit the point. Some people believe that it's > enough to add server side transformation capabilities (say, adding a > XSLT post-processor as a servlet filter!) to come up with a publishing > framework.
I guess I am one of those :) But I guess you are talking about much broader publishing needs. It is all relative. I have not used cocoon2 yet. I had very bad experiences adopting cocoon1 (right when it came out -- MacMillan's idiotsguides.com - god, I wish I could take that one back :( for many things besides cocoon's PIs - my first "real" web-site...). When I understand what I needed (too late) I realized that cocoon was the furthest thing. I am hoping to gather this info about cocoon2 from you guys (and maybe throw my 2cents in every now and then :). It sounds like you have a fantastic product. I would have installed it to play around with but all the other things you need... Then again, all the buzz makes it very interesting. I wonder if cocoon is bloatware, at least for my needs. When working with a small team (say 5-10 people spread out all over the world, well, US and England) servlets and xslt/xml seem to do everything I need. They work on it dynamicially and then generate it as a static site whenever they want. And I would bet there are few people who can create a large content-based site faster. My sites (large publishing companies) are perhaps well-suited to this though and other sites are perhaps better suited to cocoon. Why scoff something that works? Why is it a bad thing? best, -Rob --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]