[
https://issues.apache.org/jira/browse/HIVEMIND-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Johan Lindquist updated HIVEMIND-181:
-------------------------------------
Attachment: hivemind-181-192.patch
The attached patch resolves the issues about protection domain. Not sure if
the choice of using the HiveMindClassPool class as the default provider of
said domain is correct.
> Hivmind will not work in with security enforcments due to bug in Javassist
> --------------------------------------------------------------------------
>
> Key: HIVEMIND-181
> URL: https://issues.apache.org/jira/browse/HIVEMIND-181
> Project: HiveMind
> Issue Type: Bug
> Environment: IBM WebSphere 5 with Security ON
> IBM JVM
> Reporter: Renat Zubairov
> Priority: Critical
> Attachments: hivemind-181-192.patch
>
>
> Due to the bug in Javassist, ProtectionDomain wasn't associated with
> generated classes, see JIRRA from Javassist:
> http://jira.jboss.com/jira/browse/JASSIST-23
> This bug stops from executing any Hivemind based application (e.g. Tapestry)
> on the any environment with active SecurityManager.
> Unfortunately for proper fixing of this bug some changes within the Hivemind
> are required, such as (I expect)
> 1. Switch to the latest Javassist
> 2. Change all "old" method calls to the new one with additional parameter -
> Hivemind protection domain.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
