Vladimir Olenin wrote:
Browser --(request)--> WebApplication --(XML)--> Transformation Pipeline: [XML to PDF] OR [XML to HTML]
For cases where you simply want to expose the XML produced by struts to another format the combo will work great. Cocoon shines as a publishing framework and provides stuff like caching etc.
However, if you intent to produce the XML after a *series* of request/response processing (forms etc) you will have to maintain that in two frameworks instead of one, unless you only expose struts to the world and use cocoon-based views via forwards only, with both frameworks in the same webapp.
Manos --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
