tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jochen Kemnade (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (TAP5-513) Tapestry should specify the access rights it needs when a security manager is in place
Date Mon, 12 Jan 2015 08:10:39 GMT

     [ https://issues.apache.org/jira/browse/TAP5-513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jochen Kemnade closed TAP5-513.
-------------------------------
    Resolution: Invalid

We assume this is no longer relevant and therefore close it.
If you still have this issue in a recent Tapestry version (such as 5.3.8 or the latest 5.4
preview release), feel free to provide the necessary information and reopen.

> Tapestry should specify the access rights it needs when a security manager is in place
> --------------------------------------------------------------------------------------
>
>                 Key: TAP5-513
>                 URL: https://issues.apache.org/jira/browse/TAP5-513
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.1.0.0, 5.0.18
>            Reporter: Ulrich Stärk
>              Labels: bulk-close-candidate
>
> If Tapestry is used with a security manager in place, AccessControlExceptions are thrown
because Tapestry needs special permissions to do certain things.
> Tapestry should specify those access rights needed and make use of AccessController.doPrivileged()
where necessary.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message