Heh, interesting point. I guess the thing is badly named. What it really is is a missing-conversation-view-id. ie. if Seam can't restore the conversation in the request, you get redirected. Perhaps it should behave the way you are asking for, though, that could make sense.
Add a feature request to JIRA, and I'll consider the change (I'm worried about backward compatibility though).
I created a JIRA issue here: http://jira.jboss.com/jira/browse/JBSEAM-589.
IMO it doesn't matter if one transmits no or a not existing conversation id - the result is the same: no conversation is restored. Further most - if not all - pages in a pageflow rely on conversations (why would one mention the no-conversation-view-id attribute if one doesn't need a conversation?).
However, if you are worried about backwards compatibility you could perhaps add an additional parameter somewhere. Either globally in faces-config or components.xml or on a per page base in the pages.xml of pageflow files so that everyone is happy ;)
Thanks for your attention.
PS: while you are working at the pageflow stuff please have a look at http://www.jboss.com/index.html?module=bb&op=viewtopic&t=97218. IMO this would be really useful :)
I just saw that you introduced 'conversation-required' for pages.xml - thanks for that!
But how can I use that in pageflow.jpdl.xml files? I'm asking because the CVS booking demo has only pages.xml examples and there's no similar attribute in the pageflow.Page class.
If there is no conversation, then there is most definitely no pageflow. You need to put it in pages.xml. Note that it is allowed to go on a wildcard view id.
Ah, I see - i had a thinking error: thought it's using my .jpdl.xml file, but why should it if there's no cid.
Now it's working as expected - thanks again for the change :)
NP, its actually a good change. I'm using it in both the booking demo and in seam-gen.