[ http://jira.jboss.com/jira/browse/JBSEAM-790?page=all ] Shane Bryzak updated JBSEAM-790: -------------------------------- Fix Version/s: 1.1.7.GA Affects Version/s: 1.1.6.GA -- 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

[ http://jira.jboss.com/jira/browse/JBSEAM-790?page=comments#action_12352643 ] Stuart Robertson commented on JBSEAM-790: ----------------------------------------- Incidentally the same functionality would be very useful for servlet lifecycle listeners. In particular it would be very nice to be able to have Seam manage application and session binding listeners. I haven't looked into whether a similar approach might work. -- 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

[ http://jira.jboss.com/jira/browse/JBSEAM-790?page=comments#action_12352686 ] Shane Bryzak commented on JBSEAM-790: ------------------------------------- Stuart, Sorry didn't notice your comments until after I closed the issue. Can you walk me through a use case for the feature you're suggesting? -- 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

[ http://jira.jboss.com/jira/browse/JBSEAM-790?page=comments#action_12352752 ] Stuart Robertson commented on JBSEAM-790: ----------------------------------------- Hi Shane. Sure. The example I included above for instance, is for an application which is supposed to only be available during extended working hours in production. During development though, we may not want that filter to actually impose this restriction. A similar use case comes up with a filter that enforces that a user is logged on before accessing an application. Or a filter that captures timings for requests. In each case it is very nice to have Seam manage these components. Beyond DI, having Seam decide which filter implementation is actually delegated to means you can vary your filter implementations without touching web.xml. So your components.xml for dev, test and prod would specify implementations for each named filter. Web.xml would specify a DelegatingFilterProxy, supplied by Seam, which would delegate to a real filter based on the targetFilter parameter specified in web.xml. In practice, during development, when a filter's functionality isn't needed at a particular phase you could let seam inject a PassThrough filter (no-op, etc.). Or a filter that does an implicit logon. Is this enough to make it clear? To me it's nice-to-have flexibility. Not critical, but we've found that the pattern is quite simple in practice, and has been useful. -- 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