You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2011/09/14 23:28:09 UTC
[jira] [Created] (TAP5-1651) It should be possible for a
LinkCreationListener to override Tapestry and make a Link secure or
insecure after the fact
It should be possible for a LinkCreationListener to override Tapestry and make a Link secure or insecure after the fact
-----------------------------------------------------------------------------------------------------------------------
Key: TAP5-1651
URL: https://issues.apache.org/jira/browse/TAP5-1651
Project: Tapestry 5
Issue Type: Improvement
Components: tapestry-core
Affects Versions: 5.3
Reporter: Howard M. Lewis Ship
The use case here is a client who has created rules about which *paths* (not *pages*) should be secure.
This will involve adding two new methods to the Link interface; however Link is not implemented in user code, so this should not cause a problem with backwards compatibility.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (TAP5-1651) It should be possible for a
LinkCreationListener to override Tapestry and make a Link secure or
insecure after the fact
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-1651.
--------------------------------------
Resolution: Fixed
Fix Version/s: 5.3
> It should be possible for a LinkCreationListener to override Tapestry and make a Link secure or insecure after the fact
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1651
> URL: https://issues.apache.org/jira/browse/TAP5-1651
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.3
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Fix For: 5.3
>
>
> The use case here is a client who has created rules about which *paths* (not *pages*) should be secure.
> This will involve adding two new methods to the Link interface; however Link is not implemented in user code, so this should not cause a problem with backwards compatibility.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-1651) It should be possible for a
LinkCreationListener to override Tapestry and make a Link secure or
insecure after the fact
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13104989#comment-13104989 ]
Hudson commented on TAP5-1651:
------------------------------
Integrated in tapestry-trunk-freestyle #522 (See [https://builds.apache.org/job/tapestry-trunk-freestyle/522/])
TAP5-1651: It should be possible for a LinkCreationListener to override Tapestry and make a Link secure or insecure after the fact
hlship : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1170855
Files :
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/Link.java
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/LinkImpl.java
* /tapestry/tapestry5/trunk/tapestry-core/src/test/java/org/apache/tapestry5/internal/services/LinkImplTest.java
> It should be possible for a LinkCreationListener to override Tapestry and make a Link secure or insecure after the fact
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1651
> URL: https://issues.apache.org/jira/browse/TAP5-1651
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.3
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Fix For: 5.3
>
>
> The use case here is a client who has created rules about which *paths* (not *pages*) should be secure.
> This will involve adding two new methods to the Link interface; however Link is not implemented in user code, so this should not cause a problem with backwards compatibility.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (TAP5-1651) It should be possible for a
LinkCreationListener to override Tapestry and make a Link secure or
insecure after the fact
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-1651.
--------------------------------------
Resolution: Fixed
Fix Version/s: 5.3
> It should be possible for a LinkCreationListener to override Tapestry and make a Link secure or insecure after the fact
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1651
> URL: https://issues.apache.org/jira/browse/TAP5-1651
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.3
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Fix For: 5.3
>
>
> The use case here is a client who has created rules about which *paths* (not *pages*) should be secure.
> This will involve adding two new methods to the Link interface; however Link is not implemented in user code, so this should not cause a problem with backwards compatibility.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (TAP5-1651) It should be possible for a
LinkCreationListener to override Tapestry and make a Link secure or
insecure after the fact
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship reassigned TAP5-1651:
------------------------------------------
Assignee: Howard M. Lewis Ship
> It should be possible for a LinkCreationListener to override Tapestry and make a Link secure or insecure after the fact
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1651
> URL: https://issues.apache.org/jira/browse/TAP5-1651
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.3
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
>
> The use case here is a client who has created rules about which *paths* (not *pages*) should be secure.
> This will involve adding two new methods to the Link interface; however Link is not implemented in user code, so this should not cause a problem with backwards compatibility.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (TAP5-1651) It should be possible for a
LinkCreationListener to override Tapestry and make a Link secure or
insecure after the fact
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship reassigned TAP5-1651:
------------------------------------------
Assignee: Howard M. Lewis Ship
> It should be possible for a LinkCreationListener to override Tapestry and make a Link secure or insecure after the fact
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1651
> URL: https://issues.apache.org/jira/browse/TAP5-1651
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.3
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
>
> The use case here is a client who has created rules about which *paths* (not *pages*) should be secure.
> This will involve adding two new methods to the Link interface; however Link is not implemented in user code, so this should not cause a problem with backwards compatibility.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-1651) It should be possible for a
LinkCreationListener to override Tapestry and make a Link secure or
insecure after the fact
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13104989#comment-13104989 ]
Hudson commented on TAP5-1651:
------------------------------
Integrated in tapestry-trunk-freestyle #522 (See [https://builds.apache.org/job/tapestry-trunk-freestyle/522/])
TAP5-1651: It should be possible for a LinkCreationListener to override Tapestry and make a Link secure or insecure after the fact
hlship : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1170855
Files :
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/Link.java
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/LinkImpl.java
* /tapestry/tapestry5/trunk/tapestry-core/src/test/java/org/apache/tapestry5/internal/services/LinkImplTest.java
> It should be possible for a LinkCreationListener to override Tapestry and make a Link secure or insecure after the fact
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1651
> URL: https://issues.apache.org/jira/browse/TAP5-1651
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.3
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Fix For: 5.3
>
>
> The use case here is a client who has created rules about which *paths* (not *pages*) should be secure.
> This will involve adding two new methods to the Link interface; however Link is not implemented in user code, so this should not cause a problem with backwards compatibility.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira