Comments on: Wicket, Tomcat, Debian: Sometimes a little security goes way too far http://www.danwalmsley.com/2008/01/20/wicket-tomcat-debian-sometimes-a-little-security-goes-way-too-far/ Putting the nerd in comnerdedy Sun, 05 Sep 2010 13:21:40 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Al Maw http://www.danwalmsley.com/2008/01/20/wicket-tomcat-debian-sometimes-a-little-security-goes-way-too-far/comment-page-1/#comment-7082 Al Maw Tue, 22 Jan 2008 18:51:41 +0000 http://www.danwalmsley.com/2008/01/20/wicket-tomcat-debian-sometimes-a-little-security-goes-way-too-far/#comment-7082 There are some known security policies issues with Tomcat. Have you checked out the wiki article on the same: http://cwiki.apache.org/WICKET/java-security-permissions.html ? There are some known security policies issues with Tomcat. Have you checked out the wiki article on the same: http://cwiki.apache.org/WICKET/java-security-permissions.html ?

]]> By: dan http://www.danwalmsley.com/2008/01/20/wicket-tomcat-debian-sometimes-a-little-security-goes-way-too-far/comment-page-1/#comment-7046 dan Mon, 21 Jan 2008 02:29:44 +0000 http://www.danwalmsley.com/2008/01/20/wicket-tomcat-debian-sometimes-a-little-security-goes-way-too-far/#comment-7046 IInitializer for initialising plugins to our in-progress CMS framework. Basically means we can drop in components which will automatically set up their own navigation entries, database entities, etc. Means I can construct a completely customised CMS with no code and no configuration - purely dependencies. Want a new feature? Just add a maven dependency. Sweet. Only thing to do now is keep a lid on complexity and make sure our component model makes sense. Am thinking back to the hazy University days and design patterns and IoC containers... IInitializer for initialising plugins to our in-progress CMS framework. Basically means we can drop in components which will automatically set up their own navigation entries, database entities, etc.

Means I can construct a completely customised CMS with no code and no configuration – purely dependencies. Want a new feature? Just add a maven dependency.

Sweet.

Only thing to do now is keep a lid on complexity and make sure our component model makes sense. Am thinking back to the hazy University days and design patterns and IoC containers…

]]> By: Eelco Hillenius http://www.danwalmsley.com/2008/01/20/wicket-tomcat-debian-sometimes-a-little-security-goes-way-too-far/comment-page-1/#comment-7045 Eelco Hillenius Mon, 21 Jan 2008 01:39:40 +0000 http://www.danwalmsley.com/2008/01/20/wicket-tomcat-debian-sometimes-a-little-security-goes-way-too-far/#comment-7045 Too bad you're having troubles with Tomcat. Drop a note on the user list; maybe it will help others struggling with this, or maybe you'll get some good feedback. I'm using Jetty for both development and as our production server, and we never really run into much trouble (couple of times, but it was easy enough to patch ourselves, and the Jetty people fixed the issues quick after). Just wondering: what are you using IInitializer for? Too bad you’re having troubles with Tomcat. Drop a note on the user list; maybe it will help others struggling with this, or maybe you’ll get some good feedback.

I’m using Jetty for both development and as our production server, and we never really run into much trouble (couple of times, but it was easy enough to patch ourselves, and the Jetty people fixed the issues quick after).

Just wondering: what are you using IInitializer for?

]]>