Hi
I was replying to "I just wanted to get back and test the new zone and not a
entire new component."
Yes @SetupRender is not called on a zone update, Are you sure it is an ajax
update.
Try t:zone='myZone' instead of t:zone='myZone.clientId'
regards
Taha
On Thu, Apr 7, 2011 at 3:42 PM, joknroll <adjudentifr...@yahoo.com> wrote:
>
> Maybe i'm wrong too , but if the form is linked with a zone, the
> @SetupRender of the conponent is not called?
> In my case, the @SetupRender initialize the value of my param
> "messageChangeWhenSubmit".
> When I submit, I change the value of this param and update the zone to
> apply
> the new value.. so if the @SetupRender is called, the value is
> re-initialize
> ... and my test still red :(
>
> I correct my first post with the method called when validate the form (
> return the zone ):
>
> @OnEvent(value = EventConstants.VALIDATE, component = "myForm")
> public Object launchProcess() {
> something = "!! UPDATE !!";
> return myZone;
> }
>
> I have a Warning code too:
> [WARN ][12:08:21][o.a.t.s.T.ComponentInstanceResultProcessor] - Component
> demo/dummy:dummy.myzone was returned from an event handler method, but is
> not a page component. The page containing the component will render the
> client response.
>
>
> --
> View this message in context:
> http://tapestry.1045711.n5.nabble.com/Tapestry-Testify-SetupRender-launched-instead-of-update-a-zone-tp4288081p4288139.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
>
>
