Hello Ed,

Thank you for the bug report and sorry for the long delay in responding.
 I have been looking at this issue and trying to determine a reasonable
approach given that it appears to be JVM dependent.

The easiest thing from a user perspective is to drop a symlink in
/etc/tomcat6/policy.d/ to either:


The package can't merely add both symlinks, because tomcat won't start
if the target of the symlink doesn't exist.  It might be possible to
remove and then recreate the symlink in tomcat6 init script after the
JVM has been determined.

However, I'm wondering if it would be preferable to drop to add some
documentation regarding the symlink to /etc/default/tomcat6 and let the
user create the symlink when he/she enables security.

Thank you,

Attachment: signature.asc
Description: OpenPGP digital signature

This is the maintainer address of Debian's Java team
Please use
debian-j...@lists.debian.org for discussions and questions.

Reply via email to