Does anyone have any pointers relating to using Cocoon components from within another application (i.e., an in-house application), in a non-servlet based fashion?
Our aim is to produce a reporting application that takes fairly but structured XML, formats it according to various user configurable rules, and then renders it in any one (or more) of a number of outputs (primarily HTML, XML, and PDF) for display and printing. It would be a neat app if we could get it up and running, and so far, Cocoon is one possible architecture. In particular, I 'd like to know about 1) Servlet dependence (I would like to minimise this in order to make the app EJB based) 2) Performance (needs to be good, as volume would be big) 3) Restrictions (technical or otherwise that might knock this on the head) 4) Configurability (flexibility of the app from a reporting perspective is one of our key requirements) 5) Integration with other Java / XML related technologies such as FOP, SVG, Batik, etc 6) Sourcing data (primarily) from a Sybase SQL database. 7) Any other area u think might be relevant Any thoughts, ideas etc are very welcome. Thanks, Colm ********************************************************************** This message is sent in confidence for the addressee only. The contents are not allowed to be disclosed to anyone other than the addressee. Unauthorised recipients must preserve this confidentiality and should please advise the sender immediately of any error in transmission. ********************************************************************** --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
