You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Nourredine K. (JIRA)" <ji...@apache.org> on 2011/03/09 15:31:00 UTC
[jira] Created: (TAP5-1471) Provide a way to prevent overriding
services implementation
Provide a way to prevent overriding services implementation
------------------------------------------------------------
Key: TAP5-1471
URL: https://issues.apache.org/jira/browse/TAP5-1471
Project: Tapestry 5
Issue Type: Improvement
Components: tapestry-ioc
Reporter: Nourredine K.
Priority: Minor
Hello,
The idea is to prevent overriding some custom tapestry services implementation for security issues (prevent from another implementation, decorators , advisors, ... ).
Also, the usage of those services can be restricted to a subset of the features.
Nourredine.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (TAP5-1471) Provide a way to prevent overriding
services implementation
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship resolved TAP5-1471.
----------------------------------------
Resolution: Invalid
Assignee: Howard M. Lewis Ship
There is no such thing as a "security issue" in the IoC container. You, as the developer, control exactly what modules and services are running, it's not like a sneaky user can slip in some code unbeknownst to you. If you have a problem knowing what code you are running, that's an issue with your development process, not with Tapestry.
> Provide a way to prevent overriding services implementation
> ------------------------------------------------------------
>
> Key: TAP5-1471
> URL: https://issues.apache.org/jira/browse/TAP5-1471
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-ioc
> Reporter: Nourredine K.
> Assignee: Howard M. Lewis Ship
> Priority: Minor
>
> Hello,
> The idea is to prevent overriding some custom tapestry services implementation for security issues (prevent from another implementation, decorators , advisors, ... ).
> Also, the usage of those services can be restricted to a subset of the features.
> Nourredine.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (TAP5-1471) Provide a way to prevent overriding
services implementation
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship resolved TAP5-1471.
----------------------------------------
Resolution: Invalid
Assignee: Howard M. Lewis Ship
There is no such thing as a "security issue" in the IoC container. You, as the developer, control exactly what modules and services are running, it's not like a sneaky user can slip in some code unbeknownst to you. If you have a problem knowing what code you are running, that's an issue with your development process, not with Tapestry.
> Provide a way to prevent overriding services implementation
> ------------------------------------------------------------
>
> Key: TAP5-1471
> URL: https://issues.apache.org/jira/browse/TAP5-1471
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-ioc
> Reporter: Nourredine K.
> Assignee: Howard M. Lewis Ship
> Priority: Minor
>
> Hello,
> The idea is to prevent overriding some custom tapestry services implementation for security issues (prevent from another implementation, decorators , advisors, ... ).
> Also, the usage of those services can be restricted to a subset of the features.
> Nourredine.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira