|
From: <php...@li...> - 2009-07-16 23:04:35
|
Hello, Jost Thanks for your hints. Actually, the Debian Policy for packaging imposes FHS compliance. So, the JavaBridge must be installed at TomCat webapps directory. The system directories are for official libraries. But studying the tomcat system security policies (per your hints) helped to improve the /etc/tomcat5.5/policy.d/60JavaBridge.policy file. Juli logging was not configured and prevented startup. The # comment sign was not recognized at that file at a Debian Lenny clean install . Improved the rule cross platform portability. Improved the installation script sequence. The file ownership and permissions were wrong, preventing startup. So, packaging improvements were made to address these issues. Even configuring TomCat error logging does not show startup errors at /var/log/tomcat5.5/... This kind of TomCat startup errors were logged at /var/log/syslog I commited changes to CVS head today. Regards. Andre Felipe Machado http://www.techforce.com.br |