WML Postfield problem?

[Richard Lewis-Shell <rl...@mac.com>]

I'm still learning WML etc, so I may be a little off the mark here...

Postfield uses the component id as the rendered name attribute.  Because
component names must be unique, does this mean it is only possible to submit
a variable from one and only one Go?

eg. How would one extend the Hello example to have two accept options - one
to say hello, one to say goodbye, but both submitting the username variable?
(eg. assuming I want to go to a Goodbye deck instead of the Hello deck)

R

Re: WML Postfield problem?

[Richard Lewis-Shell <rl...@mac.com>]

> I'm still learning WML etc, so I may be a little off the mark here...

Yep, off the mark - ignore the rest!

> Postfield uses the component id as the rendered name attribute.  Because
> component names must be unique, does this mean it is only possible to
submit
> a variable from one and only one Go?
>
> eg. How would one extend the Hello example to have two accept options -
one
> to say hello, one to say goodbye, but both submitting the username
variable?
> (eg. assuming I want to go to a Goodbye deck instead of the Hello deck)
>
> R
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>