Getting Rid of Conversation ID on Redirect

[elmarweber.seam.elmarweber.org]

Hi,

I'm having problems getting rid of the conversation ID parameter (cid) when I use a redirect in a navigation element in pages.xml.

I'm submitting a form in the following way:

            <h:form>
                <h:commandButton action="#{bean.create()}"
                    value="#{messages['message']}" />
            </h:form>

The corresponding entry in the pages.xml looks like this:

    <page view-id="/index.xhtml">
        <navigation from-action="#{bean.create()}">
            <redirect view-id="/redirect.xhtml">
                <param name="beanId" value="#{beanId}" />
            </redirect>
        </navigation>
    </page>

When a lick on the button is performed everything works and the user is redirected to /redirect/beanId?cid=123. But how can I get rid of the conversation ID short of adding a rewrite rule? The conversation ID is a new one, not the one from the previous page, so technically not a propagation, which explains why the following tries did not work:
I tried adding <s:conversationPropagation type="none" /> to the commandButton without success. I also tried adding <param name="conversationPropagation" value="none" /> to the redirect rule (https://jira.jboss.org/jira/browse/JBSEAM-1296 (for seam 1.2)) but that just renders conversationPropagation as a parameter.

Any ideas?

Thanks and ciao,
elm

[fup]

It's possible to suppress parameters on redirects like this:

<param name="myParam" value="{null}" />
or
<param name="myParam" />

Not sure whether this is a good approach for the conversation id, but maybe it solves your problem.

[elmarweber.seam.elmarweber.org]

Thanks for the reply. The first suggestion clears the cid but still renders the cid= part in the URL. The latter let's seam Navigation classes throw an NPE an the redirect.