Wondering if anyone else is having trouble with the latest Jetspeed running under jserv? We used to run the turbine.jar, jetspeed.jar, cocoon jars, and our jars with portlets/screens in their own zone. But since Friday, all the jars/classes must be in the global classpath to run jetspeed. This is the way I have tomcat set up locally, but in our production environment we are using Jserv with seperate zones. It does work when the jars are all defined in the classpath, but doesn't this screwup auto class reloading features of jserv? jb Jeffrey D. Brekke mailto:[EMAIL PROTECTED] http://sites.netscape.net/ekkerbj/homepage ____________________________________________________________________ Get your own FREE, personal Netscape WebMail account today at http://webmail.netscape.com. -- -------------------------------------------------------------- Please read the FAQ! <http://java.apache.org/faq/> To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives and Other: <http://java.apache.org/main/mail.html> Problems?: [EMAIL PROTECTED]
