[wildfly-dev] Permissions for Arquillian in test deployments

[Tomaž Cerar]

On Thu, Sep 3, 2015 at 2:47 PM, Ondrej Kotek <okotek at redhat.com> wrote:

> There are test cases using
> org.jboss.as.arquillian.container.ManagementClient in non-runAsClient mode.
> While running with Java Security Manager without AllPermission assigned,
> the test cases fail. This is caused by insufficient permissions assigned to
> deployments -- deployments require permissions that Arquillian uses to
> create connection for ManagementClient, e.g. read FilePermission for
> modules/system/layers/base/org/jboss/xnio/nio/main/* (XNIO module),
> connect,resolve SocketPermission, * * MBeanPermission, getClassLoader
> RuntimePermission.
>

Just line of note here, ManagmentClient class you see in WildFly core tests
is not from Arquillian but WildFly core test runner.
see
https://github.com/wildfly/wildfly-core/tree/master/testsuite/test-runner/src/main/java/org/wildfly/core/testrunner

and as such, permissions could be added there at this is only used for
wildfly core testsuite.
Also, core doesn't have any dependencies to arquillian.


--
tomaz
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20150903/cf96199a/attachment.html