[
https://issues.apache.org/jira/browse/FELIX-3351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14287692#comment-14287692
]
Arjen Hoekstra commented on FELIX-3351:
---------------------------------------
I actually encountered the same issue with the 'javax.xml.bind.JAXBPermission',
which only has a 1-argument constructor. This causes AccessControlExceptions
when this permission is needed, even when it has been added correctly to the
policy file. For now, I have patched 'org.apache.felix.framework.security.jar'
using the above patch (thanks Bob for adding the patch!), but it would be nice
if this could be added to a new version, so that we don't have to maintain a
patched version ourselves.
Hope this gives a bit more background, if you would like more info, please let
me know. Thanks in advance!
> Permissions.createPermission(String name, String action, Class target) Fails
> for action == null
> -----------------------------------------------------------------------------------------------
>
> Key: FELIX-3351
> URL: https://issues.apache.org/jira/browse/FELIX-3351
> Project: Felix
> Issue Type: Bug
> Components: Framework Security
> Affects Versions: framework.security-1.4.1
> Reporter: Bob Ziuchkovski
> Assignee: Karl Pauls
> Priority: Minor
> Attachments: felix_permission_noaction.patch
>
>
> java.security.Permission has a single constructor, Permission(String name).
> While many subclasses add another constructor with sig (String name, String
> actions), this is not a requirement for Permission subclasses and custom
> permissions without the actions arg are not properly handled by
> createPermission().
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
