Some comments ...
At 11:35 AM 11/27/01 -0600, you wrote: >I'm just trying to figure out if I should take the time and create a >huge sitemap with all the functionality I want I can understand that. You want to make sure there's enough of a benefit before you put in the work. >I've also looked into >how to use servlets with Cocoon and it isn't pretty Doesn't have to be, right? You can just have your sitemap redirect to a servlet, or have a form generated by a servlet submit to cocoon. Should be able to move between servlets and cocoon quickly and easily, no? Other thoughts on this: * If you're talking about calling servlet code from Cocoon, then you might want to consider pulling the code out of the servlet into some common class that can be called both from Cocoon (from an XSP page, for example) as well as from the servlet. * You might want to consider looking into Cocoon Action classes. They're probably much easier to integrate with a Cocoon app than a servlet. >not to mention >everytime I need to add some basic functionality, I need to restart cocoon, >then httpd after tomcat restarts. Actually, you don't need to. * XSP pages and your sitemap get automatically re-compiled when changed, without restarting Cocoon/Tomcat. Similarly, changes to XML and XSL files are picked up automatically without a re-start. * Although code (e.g., Action classes) are not picked up automatically, you don't have to shut down Tomcat to reload them. Assuming that you have set up manager access, you can use the manager servlet to reload Cocoon without a shutdown (e.g., http://localhost/manager/reload?path=/cocoon) >I >could implement my navbars using taglibs instead of XInclude, which would be >easier anyway Again, your call. You'll have to decide if the benefit vs. cost of Cocoon is sufficient for you to go with it. HTH. DR --------------------------------------------------------------------- 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]>
