[
https://issues.jboss.org/browse/AS7-6577?page=com.atlassian.jira.plugin.s...
]
David Lloyd commented on AS7-6577:
----------------------------------
We should additionally support a {{jboss-permissions.xml}} descriptor with the same
schema/syntax. If such a file is present in a top-level deployment, it should take
precedence over {{permissions.xml}}; if present in a subdeployment, it should replace the
permissions for that subdeployment's code source (and any other nested JARs contained
therein) only.
Deployment descriptor parsing of META-INF/permissions.xml
---------------------------------------------------------
Key: AS7-6577
URL:
https://issues.jboss.org/browse/AS7-6577
Project: Application Server 7
Issue Type: Sub-task
Components: Security
Reporter: Anil Saldhana
Assignee: Stefan Guilhen
Fix For: 8.0.0.Alpha1
EE 6.2.2.6 Permission declarations must be stored in META-INF/permissions.xml file
within an EJB, web, or application client archive in order for them to be located
and subsequently processed by the deployment machinery of the Java EE Product.
The permissions for a library are the same as the permissions for the code that
EE.6.2.2.6.2 Permission Declaration Example
<?xml version="1.0" encoding="UTF-8"?>
<permissions>
<permission>
<classname>java.io.FilePermission</classname>
<name>/tmp/abc</name>
<actions>read,write</actions>
</permission>
<permission>
<classname>java.lang.RuntimePermission</classname>
<name>createClassLoader</name>
</permission>
</permissions>
The EE7 spec draft has a schema for permissions.xml
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira