[ https://issues.jboss.org/browse/SEAMFACES-115?page=com.atlassian.jira.plu... ] Brian Leathem commented on SEAMFACES-115: ----------------------------------------- Pulling the annotations from the @ViewConfig looks easy, and they could at that time be processed by the view extension to configure pretty faces. However, one of the goals of the ViewConfigStore is to allow configuration by multiple sources: 1) The @ViewConfig enums 2) f:metadata 3) xml (at least conceptually :) 4) JAVA API to support arbitrary user provided persistence So the goal would be to get the pretty faces rules into the ViewConfigStore, and load them into pretty faces once all configuration sources have been processed. As I understand it, pretty faces filters should to all be loaded at application start up. It doesn't really make sense to load url rewriting on first view visit, well at least not for all rewrite rules. (by all means correct me if I'm wrong) So to support this, all view config configurations have to be processed aggressively. This probably relates more to issues that will track the implementation of the other configuration sources, but I'm including it here since the pretty faces configuration is a big driver for the aggressive load. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/SEAMFACES-115?page=com.atlassian.jira.plu... ] Brian Leathem resolved SEAMFACES-115. ------------------------------------- Assignee: Brian Leathem Resolution: Done -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira