Thanks Lance,
I had to use the Environment object...,
as my hierarchy of components was the following:
PageA ---------------------------
form --------------------------
delegate ---> delegate returns the block from pageB using
ComponentSource service
=-=-=-=-=-=-=-=-
PageB ---------------------------
block -------------------------
componentA
=-=-=-=-=-=-=-=-=-
ComponentA -----------------
input (value)
So finally, I 've learned that the right way to pass the value to show from
PageA to ComponentA, and then passing back the new value (suppose the user
has modified) from ComponentA to PageA's onSuccess method
seems to be using the Environment service.
Additionally I had to embrace the input inside ComponentA with the
submitNotifier component [ I read that on Igor's book ;) ] so I could write
the value to the environment.
thanks again for the answer and let me know if you see an alternative
solution as I 'm interested to learn different ways to do things,
cheers.
Nicolás.-
On Wed, Jan 30, 2013 at 1:54 PM, Lance Java <lance.j...@googlemail.com>wrote:
> Your block will contain fields, these fields will be bound to properties in
> your page. When the form submits these page properties will be updated.
>
> You might choose to fire an event from your component via component
> resources.fireEvent() to let your page perform some action.
>
> All the normal form events will bubble up to your page too (submit,
> validate, success etc)
>
> Remember that the bubbled events will be onSuccessFromComponent() not
> onSuccessFromForm()
>
>
>
> --
> View this message in context:
> http://tapestry.1045711.n5.nabble.com/form-with-dynamic-extensible-content-tp5719671p5719672.html
> Sent from the Tapestry - User mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>
