[ https://issues.jboss.org/browse/SEAMFACES-214?page=com.atlassian.jira.plu... ] Jérémy Bogatirsky commented on SEAMFACES-214: --------------------------------------------- I think the IllegalStateException comes from the fact that '/admin' matchs various of your ViewPattern (ALL and PRIVATE). I think you should review your configuration. Jeremy -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/SEAMFACES-214?page=com.atlassian.jira.plu... ] christoph langer commented on SEAMFACES-214: -------------------------------------------- I just doublechecked with one entry only (Private) the same error occures. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/SEAMFACES-214?page=com.atlassian.jira.plu... ] christoph langer commented on SEAMFACES-214: -------------------------------------------- Thank you, very much ! Indeed i had an entry in the faces-config which triggered on the identity.login action. after removing everything works fine now! Maybe this is something that has to find a line or 2 in the documentation since many people migrate from old seam projects, looking for a feature like this and fail because of exceptions. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/SEAMFACES-214?page=com.atlassian.jira.plu... ] Bernard Labno commented on SEAMFACES-214: ----------------------------------------- IMO the problem is that the PostLoginEvent is raised during navigation SecurityPhaseListener.observePreNavigateEvent. So even adding <if>#{not facesContext.responseComplete}</if> to the navigation rule won't help, because the event is raised after rule has been selected (condition evaluated) and before rule is executed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/SEAMFACES-214?page=com.atlassian.jira.plu... ] Wulf Rowek commented on SEAMFACES-214: -------------------------------------- Workaround and possible fix: override the LoginListener by: @Specializes public class LoginListener extends org.jboss.seam.faces.security.LoginListener { @Override public void observePostLoginEvent(@Observes PostLoginEvent event) { if (!event.getFacesContext().getExternalContext().isResponseCommitted()) { super.observePostLoginEvent(event); } } } -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira