[
http://jira.jboss.com/jira/browse/JASSIST-23?page=comments#action_12340721 ]
Renat Zubairov commented on JASSIST-23:
---------------------------------------
I haven't fixed it yet in the HiveMind, the fix I've done so far to give it a try
is just associating ProtectionDomain from Javassist classes with newly loaded classes, it
just gave me oppotunity to associate loaded classes with something, but it is not a
solution for the problem in general. Should I declare old method which is not safe as
deprecated?
Java 2 Security ProtiectionDomain is not associated with new
generated classes
------------------------------------------------------------------------------
Key: JASSIST-23
URL:
http://jira.jboss.com/jira/browse/JASSIST-23
Project: Javassist
Issue Type: Bug
Environment: IBM WebSphere 5.1 with J2EE Security ON, Javassist 3.0, Tapestry
4.1, HiveMind 1.1.1
Reporter: Renat Zubairov
Assigned To: Shigeru Chiba
Priority: Blocker
Attachments: exception.txt
Original Estimate: 3 hours
Remaining Estimate: 3 hours
Classes that are generated using Javassist have no associated protection domain therefore
it is not possible for JVM to assign permissions based on the static JAR files names, this
is severe problem because it is not possible to grant permissions, hence all permissions
are vorbidden, since that nothing works.
Javassist is used by HiveMind to generate proxy classes for it's services, an see the
stack trace (in attachment) the generated classes can't be associated with any
ProtectionDomain, therefore
_any Javassist supported application is impossble to start under strict security in
Java_.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira