Understanding Conversation scope and how it works

[hirowla.ian.rowlands.three.com.au]

Hi, just wanting to clarify my understanding of Conversation scope and what it can do for me. I have an example JSF2 application fragment which I'll use as follows:

I have a login prompt on a welcome screen. I have no validation on the fields there. The action calls a method on a bean, which is ConversationScoped. If the login fails (usually because the username is invalid), I want to redirect the user to another (login) screen where the username is validated (using BeanValidation), and take the username they entered onto the new screen.

I have a separate method for logging in from the welcome screen. When it fails there, I make the conversation non-transient. I then copy the username into a new field, which is displayed on the new screen. I then redirect to the new screen using a format like "login?faces-redirect=true&cid=<conversion ID>".

Given I have made the conversation non-transient and am supplying the conversation ID to the new URL, I would think I should be getting the same bean back when I call a method on that bean. But this isn't the case - I seem to be getting a new bean, which is exactly what I am trying to avoid.

Am I missing something obvious here, or don't I understand the conversation scope properly?

Thanks,

Ian

[nickarls]

Have you outputted the cid:s and debugged? It could be a case of where the old conversation is already destroyed as transient and you are actually promoting a fresh one?

[hirowla.ian.rowlands.three.com.au]

Thanks for your suggestion. I misunderstood what to do with the conversation ID. I thought that I needed to set the ID when I made it non-transient. Of course my login bean was connected to the ID which was originally set, so it wasn't coming up. So when I left the ID alone, the bean expected came back.

Also, as an answer to your quote - yes, you are and you should apologize to her for whatever you've done.

Thanks,

Ian