[ https://issues.jboss.org/browse/SEAMFACES-122?page=com.atlassian.jira.plu... ] Brian Leathem commented on SEAMFACES-122: ----------------------------------------- With this enum/@ViewPattern coupling, we could have @LoginViewId refernece another enum value, rather than a string -- 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-122?page=com.atlassian.jira.plu... ] Lincoln Baxter III commented on SEAMFACES-122: ---------------------------------------------- This would probably be simplest using a two-part strategy for navigation. The combination of a Utility class and a JSF NavigationHandler. For instance: {code}@Inject private Navigator nav;{code} {code}public String myAction() { /* * Redirect to (HTTP GET) the specified view. (faces-redirect=true) */ return nav.redirectTo(viewEnum); /* * Navigate (JSF) to the specified view. */ return nav.navigateTo(viewEnum); /* * Return a NavigationBuilder, then navigate (JSF) to the specified view. */ return nav.toView(viewEnum).navigate(); /* * Return a NavigationBuilder, add a ?query=parameter, then redirect (HTTP GET) to the specified view. */ return nav.toView(viewEnum).addParameter("p", value).redirect(); /* * Return a NavigationBuilder, add a ?query=parameter, then navigate (JSF) to the specified view. */ return nav.toView(viewEnum).addParameter("p", value).navigate(); }{code} This relies on the Navigator to serialize any navigation information into String form so that it may be consumed by a custom NavigationHandlerImpl provided by Seam Faces and registered in faces-config.xml. -- 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-122?page=com.atlassian.jira.plu... ] Lincoln Baxter III commented on SEAMFACES-122: ---------------------------------------------- This should probably support two modes of interaction: 1. Return a faces navigation string. 2. Actually invoke NavigationHandler and perform the navigation (for use in other artifacts that do not already have hooks into Faces navigation) -- 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-122?page=com.atlassian.jira.plu... ] Brian Leathem commented on SEAMFACES-122: ----------------------------------------- Note: Conversation propagation is being address in WELD-919 and CDI-135. If Seam Faces gets to it first, we may want to prototype this functionality in a custom navigation handler, but we should stick with the syntax agreed upon in the upstream issues. -- 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-122?page=com.atlassian.jira.plu... ] Brian Leathem commented on SEAMFACES-122: ----------------------------------------- This API should align with the "http redirect" proposal in SEAMFACES-196 and SEAMSERVLET-44. Perhaps the navigator element could encompass the proposed FacesManager functionality from SEAMFACES-196, and delegate "http redirects" to SEAMSERVLET-44. -- 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-122?page=com.atlassian.jira.plu... ] Brian Leathem updated SEAMFACES-122: ------------------------------------ Comment: was deleted (was: Stuart Douglas suggests: {quote} using getResource() to get the location of a known resource (e.g. the extension class itself) then from there figure out the path to the web.xml {quote}) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira