i have been working with seam for quit some time now but i can't get this one right.
i have a login.xhtml page that logs in using seam identity. i have an inbox.xhtml page that uses a static named conversation (it's kind of the main conversation,
inboxConversation=main
). on succesful login, i have a page configuration to redirect to the inbox.xhtml page.
<navigation from-action="#{identity.login}">
<rule if="#{identity.loggedIn}">
<begin-conversation join="true" />
<redirect view-id="/up/inbox.xhtml"></redirect>
</rule>
</navigation>
it all works nicely well, each time i browse back to the inbox page i pick up the conversation, data is nicely cashed inside.
however, when the user goes back to the login.xhtml page without logging out. and tries to log in again, i than get a conversation already in use
exception.
it seems that the login does not really relogin if already authenticated (as i can see from the identity.java code) but something must happen with the conversations as seam does not want to 'join' the static conversation in this specific flow.
it feels like a bug. any comments?