[
https://issues.apache.org/jira/browse/FELIX-2993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13051125#comment-13051125
]
Andrei Pozolotin commented on FELIX-2993:
-----------------------------------------
Karl:
re: "It can't do that if there is one already (this is expected as per spec)."
this is what it says:
core-4.2-9.6
The Framework must replace the Security Manager to implement the Con-
ditional Permission Admin in a compliant implementation. If a Framework
implementation is not able to take over the Security Manager because
another party in the VM has already set it, then not all features of this speci-
fication can be implemented.
this is how I understand it:
a) try System.setSecurityManager(osgiSecrurityManager)
b) if SecurityException -> give up
this is what felix is doing now:
a) if (System.getSecurityManager() != null)
b) -> give up
this does not sound like "must replace"
> jnlp & felix.security
> ---------------------
>
> Key: FELIX-2993
> URL: https://issues.apache.org/jira/browse/FELIX-2993
> Project: Felix
> Issue Type: Bug
> Components: Framework Security
> Reporter: Andrei Pozolotin
>
> original thread:
> http://www.mail-archive.com/users@felix.apache.org/msg10424.html
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
