Take then the latest 6 5 is getting pretty old On 1/21/08, Martijn Dashorst <[EMAIL PROTECTED]> wrote: > You might want to skip the packaged version (IMO linux packagers don't get > the Java packaging), and just unzip a tarball in /opt/tomcat/tomcat-5.5.20 > Then you are in complete control over how the server runs. > > Martijn > > On 1/21/08, Daniel Walmsley <[EMAIL PROTECTED]> wrote: > > > > I blogged this, and Eelco wisely suggested I post it here. This is both a > > warning and plea for help - what's the best way to configure Tomcat on > > Debian for Wicket? > > > > > > Was up until 3am last night banging my head against another frustrating > > go-nowhere issue deploying Wicket on Debian Etch's default Tomcat5.5. > > > > > > Apparently the latest version (5.5.20-2etch1) has additional security > > headaches features which prevent wicket from functioning properly > > out-of-the-box: > > > > > > * First of all, there's still an (as-yet-unsolved) mystery around why > > I couldn't get Wicket to start up as a filter. Just the mysterious "ERROR: > > filterStart" which makes me want to feed Tomcat to angry lions. Worked > > around it by using Wicket in Servlet mode instead. > > * Tomcat's juli.jar can't access WEB-INF/classes/logging.properties. > > Fixed (in sledgehammer-like way) by adding "permission > > java.security.AllPermission;" to > > /etc/tomcat5.5/policy.d/03catalina.policy, in the Juli section. > > * Tomcat security prevents webapps from accessing all sorts of > > features and methods by default, including wicket.properties, methods > > inside shipped jars, etc. Not being a Tomcat expert, and trusting the > innate > > security of the server and millions of lines of third party code (i.e. I'm > > an idiot) I again just popped a java.security.AllPermission; in > > appropriate spots in /etc/tomcat5.5/policy.d/04webapps.policy. Let the > > flames commence! > > > > > > If Tomcat was a little more helpful in its error messages, this would > > never have been so painful. Jetty has always run my Wicket apps without > > complaint (though I've never tried the official Debian Jetty packages - > > maybe they're crippleware secure too?). > > > > > > The only reason I use Tomcat at all is the remote management and > > deployment features, which are well-supported by Cargo. Now that these > > issues are out of the way (mostly) I can take another few steps towards my > > dream of a seamless, fire-and-forget, auto-deploying, smoke-tested, > > pluggable and modular web app deployment system. > > > > > > Any ideas on how to better configure Tomcat? > > > > > > Any ideas on how to get more information about that ERROR: filterStart > > problem? I'd really like to do things the recommended way, instead of > having > > to use WicketServlet. > > > > > > Cheers, > > Dan > > > > *Daniel Walmsley > > Director, Firesyde <http://firesyde.com/> > > e: [EMAIL PROTECTED] > > m: +61404864141 > > * > > > > > > > > > > > > -- > Buy Wicket in Action: http://manning.com/dashorst > Apache Wicket 1.3.0 is released > Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0 >
-- Sent from Gmail for mobile | mobile.google.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
