[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-1296) Add <propagation type=""/> element to <redirect/> / <render/> in pages.xml

[Pete Muir (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBSEAM-1296?page=all ]

Pete Muir updated JBSEAM-1296:
------------------------------

        Summary: Add <propagation type=""/> element to <redirect/> / <render/> in pages.xml  (was: Add <propagation type="?"/> as a child to <rule> or <redirect/> / <render/> in pages.xml)
    Description: 
While you can add a the propagation via a parameter its a bit verbose and cluttered (due to the value binding string literal) 

<page view-id="/editDocument.xhtml">
    
    <navigation from-action="#{documentEditor.update}">
        <rule if="#{documentEditor.errors.empty}">
            <end-conversation/>
            <redirect view-id="/viewDocument.xhtml">
                <param name="conversationPropagation" value="#{'none'}"/>
            </redirect>
        </rule>
    </navigation>
    
</page>

Adding a <propagation type="?"/> would be much clearer.

<page view-id="/editDocument.xhtml">
    
    <navigation>
        <rule if-outcome="done">
            <end-conversation/>
            <redirect view-id="/viewDocument.xhtml">
                <propagation type="none"/>
            </redirect>
        </rule>
    </navigation>
    
</page>


Side note : 
The reason for needing to control the propagation in the circumstance above is so that the target view (/viewDocument.xhtml) can start with a new clean conversation. The redirect mechanism delays the end of the conversation untill it gets to the redirected to view, but I dont want that conv to be used. The before-redirect attribute doesnt work in this case as the redirect url needs to include data from the existing conversation (page parameters). I use the same scenario in other places via s:link/s:button but I cannot do this here as its dependent on the outcome not what link/button I pressed

  was:
While you can add a the propagation via a parameter its a bit verbose and cluttered (due to the value binding string literal) 

<page view-id="/editDocument.xhtml">
    
    <navigation from-action="#{documentEditor.update}">
        <rule if="#{documentEditor.errors.empty}">
            <end-conversation/>
            <redirect view-id="/viewDocument.xhtml">
                <param name="conversationPropagation" value="#{'none'}"/>
            </redirect>
        </rule>
    </navigation>
    
</page>

Adding a <propagation type="?"/> would be much cleaer.

<page view-id="/editDocument.xhtml">
    
    <navigation>
        <rule if-outcome="done">
            <end-conversation/>
            <redirect view-id="/viewDocument.xhtml">
                <propagation type="none"/>
            </redirect>
        </rule>
    </navigation>
    
</page>


Side note : 
The reason for needing to control the propagation in the circumstance above is so that the target view (/viewDocument.xhtml) can start with a new clean conversation. The redirect mechanism delays the end of the conversation untill it gets to the redirected to view, but I dont want that conv to be used. The before-redirect attribute doesnt work in this case as the redirect url needs to include data from the existing conversation (page parameters). I use the same scenario in other places via s:link/s:button but I cannot do this here as its dependent on the outcome not what link/button I pressed


> Add <propagation type=""/> element to <redirect/> / <render/> in pages.xml
> --------------------------------------------------------------------------
>
>                 Key: JBSEAM-1296
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-1296
>             Project: JBoss Seam
>          Issue Type: Feature Request
>          Components: Core
>    Affects Versions: 1.2.1.GA, 1.2.0.GA
>            Reporter: Chris Rudd
>
> While you can add a the propagation via a parameter its a bit verbose and cluttered (due to the value binding string literal) 
> <page view-id="/editDocument.xhtml">
>     
>     <navigation from-action="#{documentEditor.update}">
>         <rule if="#{documentEditor.errors.empty}">
>             <end-conversation/>
>             <redirect view-id="/viewDocument.xhtml">
>                 <param name="conversationPropagation" value="#{'none'}"/>
>             </redirect>
>         </rule>
>     </navigation>
>     
> </page>
> Adding a <propagation type="?"/> would be much clearer.
> <page view-id="/editDocument.xhtml">
>     
>     <navigation>
>         <rule if-outcome="done">
>             <end-conversation/>
>             <redirect view-id="/viewDocument.xhtml">
>                 <propagation type="none"/>
>             </redirect>
>         </rule>
>     </navigation>
>     
> </page>
> Side note : 
> The reason for needing to control the propagation in the circumstance above is so that the target view (/viewDocument.xhtml) can start with a new clean conversation. The redirect mechanism delays the end of the conversation untill it gets to the redirected to view, but I dont want that conv to be used. The before-redirect attribute doesnt work in this case as the redirect url needs to include data from the existing conversation (page parameters). I use the same scenario in other places via s:link/s:button but I cannot do this here as its dependent on the outcome not what link/button I pressed

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira