Tellis You ask "is cocoon good for static pages or can it be used for highly interactive dynamic pages?" Very short version answer is: Yes, Cocoon can be used for both. Slightly longer: Cocoon essentially *is* a servlet, designed to enable the creation of XML (from static files, databases, web services or other sources) and provide an efficient and effective framework for manipluating that XML into a variety of output formats (including all the ones you list). Cocoon works whether you have a single file or a whole multitude with any combination of static or dynamic. Even longer (from the Cocoon Home Page at: http://xml.apache.org/cocoon/) Designed for performance and scalability around pipelined SAX processing, Cocoon offers a flexible environment based on a separation of concerns
between content, logic, and style. Cocoon's centralized configuration system helps you to create, deploy, and maintain rock-solid XML server applications. Cocoon interacts with most data sources, including filesystems, RDBMS, LDAP, native XML databases, and network-based data sources. It adapts content delivery to the capabilities of different devices like HTML, WML, PDF, SVG, and RTF, to name just a few. You can run Cocoon as a Servlet as well as through a powerful, commandline interface. The deliberate design of its abstract environment gives you the freedom to extend its functionality to meet your special needs in a highly modular fashion. By now this should have answered your question (but you probably have others!) - look through the Overview ( http://xml.apache.org/cocoon/overview.html ) and browse from there - also look at the http://wiki.cocoondev.org/Wiki.jsp?page=Main Wiki site; mostly maintained by folk who also asking questions and trying to explain what they find to others... >>> [EMAIL PROTECTED] 27/01/2003 12:16:04 >>> Hi, I am quite new to cocoon. I am evaulating web publishing frameworks for my company. Although Cocoon sounds very promising I am not entiely sure because the pages in my web application are not static. All of them are dynamically generated on the fly. The backend services although still under design may be developed using JINI, object databases, LDAP etc.... The main reason why I was drawn to cocoon was its multichanel capabilities. We may want to target the pages to a number of devices - mobiles, PDAs, PCs etc.... My original (very simplistic) design was to simply have servlets generate XML and then transform these using XSLT. This is where I thought cocoon would help. My question is - is cocoon good for static pages or can it be used for highly interactive dynamic pages? Regards Tellis _________________________________________________________________ Stay in touch with absent friends - get MSN Messenger http://messenger.msn.co.uk --------------------------------------------------------------------- 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]> -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. "The CSIR exercises no editorial control over E-mail messages and/or attachments thereto/links referred to therein originating in the organisation and the views in this message/attachments thereto are therefore not necessarily those of the CSIR and/or its employees. The sender of this e-mail is, moreover, in terms of the CSIR's Conditions of Service, subject to compliance with the CSIR's internal E-mail and Internet Policy." --------------------------------------------------------------------- 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]>
