[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1544) Extend @Restrict annotation to allow specifying the "actionthe "args" parameter fro hasPermission a valuebinding for the instance instead of always passing null.

Extend @Restrict annotation to allow specifying the "actionthe "args" parameter fro hasPermission a valuebinding for the instance instead of always passing null. ----------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-1544 URL: http://jira.jboss.com/jira/browse/JBSEAM-1544 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 1.3.0.ALPHA Reporter: Chris Rudd I'm currently using a decendant of the Home objects that uses the specifis @Restrict on the update/persist and remove methods. The different Home objects are defined via configuration. This all works great, except that there isnt a way to get at the particular instance that the Home object is operating on. One could provide additional attributes to the @Restrict annotation such that one can specify the instance parameter of thte default s:hasPermission() that gets generated. Additionally the "root" object (the component that the interceptor is running against) would need to be exposed so that it can be accessed genericly (this would be due to the defining of the Home object via configuration, where the annotation has to be the same for every instance). I suggest "component" as the name to bind it to : i.e. @Restruct(instance=#{componet.instance}) . This would expose the current component as "component" then the createDefaultExpr would produce "#{s:hasPermission(<component name>, <method name>, compoent.instance)}" Additionally it would be nice to ve able to override the "action" to use (instead of always using the method name). -- 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