That's not a workaround, it's a matter of what is called first.
In theory it could be both things, however I realized that you're right that
it's not a workaround when I compare it to the structure outlined by Geoff,
which sounds like the proper structure. It was sounding to me like a
Hi, thanks for the clarifications.
If these values are used in the initial page rendering, as it's the case here,
you don't need to @Persist them at all. The values of the fields will be kept
until the request is finished.
(Just a detail) I was thinking @Persist because if I had to calculate
Nope, it looks like none of the methods executed during the Rendering Phases or
the Page Life Cycle can update a zone. Which makes sense considering what I
have been explained here about updating zones.
Considering that, I realized that my kind of problem is not that much about
zones. I would
On Wed, 26 Mar 2014 08:25:40 -0300, Davide Vecchi d...@amc.dk wrote:
1) I have a getter that might cause an error.
2) This getter gets called for the first time by Tapestry, during page
rendering (because its value must already appear in the page, before any
possible user action).
3) If
Thanks for the pointers about onException and @Cached, I didn't know either.
@Cached would allow me to avoid wrapping the getter body in an if
(this.myValue == null).
onException would help my case only if it was possible to update a zone from
that method even if the exception that triggered
On Wed, 26 Mar 2014 10:44:05 -0300, Davide Vecchi d...@amc.dk wrote:
Anyway, maybe you should rethink the way you handle your exceptions.
Shouldn't they be treated inside the getter methods themselves?
I'm very confused about this suggestion. Am I not doing exactly that ? I
mean, treating
I think David may need to start from scratch...
First, render a page with no errors. The template can include a zone. Notice
that the zone is rendered too. It defines an area that the server can now
refresh - but only in response to an AJAX request.
You can set up the fields on before you
Sorry for the double post. After I posted the first one I realized I had
unsubscribed from the mailing list some time ago, so I subscribed and sent the
question again. I thought the one I had sent while unsubscribed wouldn't show
up (it hadn't at that time). My apologies.
-Original
Hi!
On Tue, 25 Mar 2014 08:26:33 -0300, Davide Vecchi d...@amc.dk wrote:
I have a zone to show possible errors that might occur in a get* method
called by Tapestry during page rendering to retrieve the value for a
property (String myValue in the example below).
Why do you want for that to
Not sure if I'm understanding your sequence, but I don't see an AJAX
request there. Tapestry can return zone(s) in response to an AJAX request
(ie. XHR). Do these help?
http://jumpstart.doublenegative.com.au/jumpstart/examples/ajax/eventlink
Hi,
You're trying to use AjaxResponseRenderer during the initial render of the
zone, which is a normal, full-page, non-AJAX request, not when the zone is
being updated during an AJAX request. In addition, your getter, which is
the method that sets the error message, is only invoked
On Tue, 25 Mar 2014 12:33:30 -0300, Davide Vecchi d...@amc.dk wrote:
Hi,
Hi!
The jumpstart examples linked by Geoff Callender are also useful but
they show how to update a zone in response to a user's action (clicking
on a link or button) while in my case I need to update a zone in
12 matches
Mail list logo
