Sure we can reopen. As for a fix, it may need to come from another contributor, my plate is pretty full right now, sorry.
I agree with Bernard. This is a very common use case. The JSF technique for handling redirect after login is a navigation rule, which conflicts fatally with @ViewConfig.
The following are incompatible:
{code}
@ViewConfig
public interface PagesConfig {
static enum Pages
{
@FacesRedirect
@ViewPattern("/view/*")
@LoginView("/login.xhtml")
@LoggedIn
ALL,
@FacesRedirect
@ViewPattern("/login.xhtml")
LOGIN
}
}
{code}
{code:xml}
<navigation-rule>
<navigation-case>
<from-action>#{identity.login}</from-action>
<if>#{identity.loggedIn}</if>
<to-view-id>/view/home.xhtml</to-view-id>
<redirect/>
</navigation-case>
<navigation-case>
<from-action>#{identity.login}</from-action>
<from-outcome>failed</from-outcome>
<to-view-id>/login.xhtml</to-view-id>
</navigation-case>
</navigation-rule>
{code:xml}