[jira] [Updated] (TAP5-513) Tapestry should specify the access rights it needs when a security manager is in place

["Jochen Kemnade (JIRA)" <ji...@apache.org>]

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

Jochen Kemnade updated TAP5-513:
--------------------------------

    Labels: bulk-close-candidate  (was: tapestry5-review-for-closing)

This issue has been last updated about 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future.

If the issue still persists with the most recent development preview of Tapestry (5.4-beta-6, which is available from Maven Central), please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the dev@tapestry.apache.org mailing list first.


> 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.2#6252)