page navigation externalisation

[Frederic Do Couto <fr...@gmail.com>]

Hi,

I wonder if there is a mecanism to externalise the navigation.
I mean, instead of having explicitly cycle.activate("myNextPage"), I
would have cycle.activate(someMecanism.getNextPage(fromHere,
"success", ...)) ?


Thank you,

Frederic.

---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org

Re: page navigation externalisation

[Nemanja Kostic <n....@youngculture.com>]

Yes.

In your class file you could put something like:

    if (success)
        cycle.activate(getSpecification().getProperty("success"));

    if (error)
        cycle.activate(getSpecification().getProperty("error"));


And in page specification just define that property, like:

	<property name="success" value="Home" />
        <property name="error" value="Error" />



Nemanja.



Frederic Do Couto wrote:

>Hi,
>
>I wonder if there is a mecanism to externalise the navigation.
>I mean, instead of having explicitly cycle.activate("myNextPage"), I
>would have cycle.activate(someMecanism.getNextPage(fromHere,
>"success", ...)) ?
>
>
>Thank you,
>
>Frederic.
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>  
>


---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org