Page: http://wiki.cocoondev.org/Wiki.jsp?page=SpecificDatabaseConnectionNew , version: 21 on Wed Jun 4 07:32:48 2003 by AntonioGallardo
- !!Comments from the readers - - I think the db separator for postgres is "/" and not ":" - - eg. jdbc:postgresql://YourServerName:5432/DB_Name - Page: http://wiki.cocoondev.org/Wiki.jsp?page=EndorsedLibsProblem , version: 6 on Wed Jun 4 07:58:55 2003 by SylvainWallez - Fortunately, the JDK [provides a mechanism|http://java.sun.com/j2se/1.4.1/docs/guide/standards/index.html] to solve this problem : libraries shipped with the JDK can be upgraded by putting the updated libraries either in the {{jre/lib/endorsed}} libraries, or in a path given using the {{java.endorsed.dirs}} JVM argument. ? - + Fortunately, the JDK [provides a mechanism|http://java.sun.com/j2se/1.4.1/docs/guide/standards/index.html] to solve this problem: libraries shipped with the JDK can be upgraded by putting the updated libraries either in the {{jre/lib/endorsed}} libraries, or in a path given using the {{java.endorsed.dirs}} JVM argument. - So you can put new versions of Xalan and Xerces there. But changing the configuration of the JDK is not something that you may want to do when you deploy a web application. + So you can put new versions of Xalan and Xerces there. But changing the configuration of the JDK is not something that you may want to do when you deploy a web application (also your sysadmin and/or hosting provider may not allow it). ? ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ - Fortunately (again), Tomcat startup scripts automatically sets {{java.endorsed.dirs}} to {{''tomcat-home''/common/endorsed}}. This means you just have to put the new jars here and not in the JDK. + Fortunately (again), Tomcat startup scripts automatically sets {{java.endorsed.dirs}} to {{''tomcat-home''/common/endorsed}}. This means you just have to put the new jars there and not in the JDK. ? + - However (this story never ends), you may encounter the following problem : two different webapps running on the same Tomcat require each a different version of Xalan ! What's the solution, then? Installing each application in a different Tomcat could be the solution, but requires yet another JVM to run on the server (not to mention the additional system maintainance for startup and shutdown). ? - ^ - + However (this story never ends), your sysadmin may not let you modify the serlvet engine configuration, or you may, as I did, encounter the following problem: two different webapps running on the same Tomcat requiring each a different version of Xalan! What's the solution, then? Installing each application in a different Tomcat could be the solution, but requires yet another JVM to run on the server (not to mention the additional system maintainance for startup and shutdown). ? ++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ^^^ - Cocoon provides an alternate servlet named {{ParanoidCocoonServlet}}. What this servlet does is create a special classloader, then use it to load and run the standard {{CocoonServlet}}. + To finally solve this annoying problem, Cocoon provides an alternate servlet named {{ParanoidCocoonServlet}}. What this servlet does is create a special classloader, then use it to load and run the standard {{CocoonServlet}} in an sandbox that shields it from other libraries lying around in the system. ? ++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
