tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 37882] - ClassCircularityError when principal included in security policy
Date Mon, 17 Apr 2006 23:36:53 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=37882>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=37882





------- Additional Comments From james.woods@symbionetworks.com  2006-04-17 23:36 -------
(In reply to comment #3)
> Suggested patch?

We've since written our own policy implementation that bypasses the Sun
implementation (we were going to do this anyway as we wanted to use a database
as our policy repository). Our hack to get around the ClassCircularityError is
to always grant java.io.FilePermission, java.lang.RuntimePermission
"accessClassInPackage", and java.lang.RuntimePermission "defineClassInPackage"
when the file or class in question relates to our Principal class. Not very
elegant I know but it works for us.

If we could get access to the Sun policy implementation source code we might be
able to work out why the error occurred in the first place.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message