Page Parameters and Expired Conversations

[iradix]

A quick question about page parameters. As I understand it, they are available so that conversational state can be reinitialized when the conversation no longer exists, like when a page is accessed from a bookmark. If that's the case, then shouldn't there be a way to override Seams default behaivour of adding org.jboss.seam.NoConversation to the faces messages if an expired conversation is encountered? Right now I'm trying to use the feature to make product pages bookmarkable and it isn't going to inspire shopper confidence to see "Conversation Expired" when trying to decide whether to click "Add to Cart"........ I also realize this is a new feature and am happy to help make it a bit more robust but I wanted to see what the plans were before digging into the code.

[gavin.king]

Well, I guess you could use them that way - but they are really meant to be used *instead* of conversations, when you need bookmarkability.

You can change that message logic by extending the built-in component and overriding, or by adding a key to the page-scoped resource bundle in the new Seam release.