[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2608) Natural conversation for wildcard view-id

[Pete Muir (JIRA)]

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

Pete Muir updated JBSEAM-2608:
------------------------------

    Fix Version/s: 2.1.0.BETA2
                       (was: 2.1.0.GA)

> Natural conversation for wildcard view-id
> -----------------------------------------
>
>                 Key: JBSEAM-2608
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-2608
>             Project: Seam
>          Issue Type: Feature Request
>          Components: Core
>    Affects Versions: 2.0.1.GA
>            Reporter: Jacob Orshalick
>             Fix For: 2.1.0.BETA2
>
>
> When a natural conversation spans a number of pages you currently have to explicitly state the named conversation for each view-id. It would be nice to simply specify the natural conversation for a wildcard view-id.
> For example, if my conversation spans the following:
> Code:
> <conversation name="Checkout"
>                   parameter-name="cart"
>                   parameter-value="#{cart.cartId}"/>
> <page view-id="/checkout/checkout1.jsp" conversation="Checkout" />
> <page view-id="/checkout/checkout2.jsp" conversation="Checkout" />
> <page view-id="/checkout/checkout3.jsp" conversation="Checkout" />
> <page view-id="/checkout/confirm.jsp" conversation="Checkout" />	
> Instead I would prefer to use:
> Code:
> <page view-id="/checkout/*" conversation="Checkout" />	
> This is also especially useful for free navigation situations within the conversation that do not have navigation rules (i.e. the conversation spans many pages but can access any page at any time) to avoid specifying each view-id in pages.xml.

-- 
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