[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-836) Security interceptor should not be triggered for lifecycle methods
Gavin King (JIRA)
jira-events at lists.jboss.org
Tue Feb 13 01:08:30 EST 2007
[ http://jira.jboss.com/jira/browse/JBSEAM-836?page=all ]
Gavin King updated JBSEAM-836:
------------------------------
Component/s: Security
> Security interceptor should not be triggered for lifecycle methods
> ------------------------------------------------------------------
>
> Key: JBSEAM-836
> URL: http://jira.jboss.com/jira/browse/JBSEAM-836
> Project: JBoss Seam
> Issue Type: Bug
> Components: Security
> Affects Versions: 1.1.5.GA, 1.1.6.GA
> Reporter: Gavin King
> Assigned To: Gavin King
> Priority: Critical
> Fix For: 1.1.7.GA
>
>
> For lifecycle methods, especially @Destroy, class-level restrictions should be ignored. Currently the booking example stacktraces when you try to log out.
> Use Component.isLifecycleMethod(method)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the seam-issues
mailing list