It may be an unusual approach for Cocoon, but Cocoon is the only apache project that expects applications to be built this way. So Cocoon is unusual with respect to all other framework components.
I don't find Cocoon complex from a build perspective, just a pain in the rear. Every new cocoon release I incorporate requires that I do a diff between the old sitemap and the new sitemap so that I can incorporate the changes into my sitemap. Likewise with cocoon.xconf. Yes, I know there are tools that can help with this, and Geoff's procedures would proably help - but I shouldn't have to do this at all. I read the link regarding cocoon blocks and it seems like it is moving off in a direction I'm not sure I'm comfortable with - or at least, I don't see how it solves my issues. The main issue here seems to be the view that Cocoon is analogous to a servlet container. I don't see it quite that way, but even if I did, I don't know of a servlet container that requires I use its build scripts to build my application. I view Cocoon as simply a framework. Yes, my application runs within the context of that framework, but just because Cocoon providess the servlet that doesn't mean that Cocoon is the application. The application is the result of the Cocoon framework, any other frameworks I require, my pipeline, my components and their configuration, my web-app configuration, and my build process. Please don't misunderstand me. I looked at various alternatives to Cocoon and none of them made any sense to me given the requirements of our application. I have written a couple of components that I would love to give to the project - one is a BeanGenerator that uses the Betwixt SAXBeanWriter to get arbitrary ValueObjects generated by the EJB container into the pipeline. Another is a Properties component that allows me to create a Properties object via definitions in cocoon.xconf. I then configure various BeanGenerator instances with the Properties component's role so that it can pass the Properties object to the constructor of the business delegate that creates the bean. At this point I would say I'm a Cocoon expert, but I don't believe I am a novice either. Believe me, if I had the time to come up with a proper solution to the issues I am raising and could implement them, I'd happily contribute them. Ralph > -----Original Message----- > From: Antonio Gallardo [mailto:[EMAIL PROTECTED] > Sent: Sunday, August 17, 2003 1:07 AM > To: [EMAIL PROTECTED] > Subject: RE: [ANN] Apache Cocoon 2.1 Released - binary?? > > Pardon me for being rude, but I really don't care. I will > not integrate > > my project into cocoon (i.e - use Cocoon's build to build > my webapp). I > > WILL integrate the cocoon framework into my project. > > This is another history and a non-usual approach using cocoon. I think > this is why you think cocoon is complex. I invite you to find > the way how > to do the integration. > > Best Regards, > > Antonio Gallardo --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
