thanks for your response, Peter ;-) .... difficult questions ... I would like to explain my purposes a little more ( although I don't know if it's necessary for me or for you ... I think for me ;-) )
My webapp is a vertical app on cocoon, specifically only oriented for Businesses who wants to base their e-comm-activity in CRM. The architecture of Cocoon, based entirely on XML, makes it very good for my purposes. My problem is that I not only need to create content on Cocoon but I need to create a new layer of services/components on Cocoon, layers nearest to requirements for Businesses and CRM and in other concern areas different to cocoon but I would like to make it as Cocoon makes it (and avalon) ( here is my problem, you know ;-) ), In this sense, the result should be a Cocoon but with enhanced services for the purposes mentioned, strongly based in cocoon but with developing future-jobs parallel to Cocoon because her high-specificity. In a very general overview, my webapp will need to make use of cocoon facilities and architecture, EJB and DB (and to create XML from DB) and it should conform her as a Business2CRM Webpublishing framework (I'll try it ;-) ) Like you said me I would appreciate any article or information that can help me to clarify my doubts concerned to Cocoon vs webapps. Also comments about these explanations. Also thank's a lot for your hints about XML - XSLT concerns, Peter. Raśl Cruz [EMAIL PROTECTED] --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
