IMHO, I think it's helpful to indicate when and why you're instantiating
UserProfile, rather than just conditioning by "is null".
void onPrepareForRender() throws Exception {
// If fresh start, make sure there's a UserProfile object available.
if (form.isValid()) {
I'm nodding enthusiastically as I read Kalle's comments. He's right - the
differences between being in an authenticated state and non-authenticated state
are so significant and it simplifies matters if a page can assume it is dealing
with just one state or the other. I should have mentioned this
On Tue, Oct 14, 2014 at 11:11 AM, George Christman
wrote:
> Commented inline
> On Tue, Oct 14, 2014 at 12:15 PM, Kalle Korhonen <
> kalle.o.korho...@gmail.com
> > wrote:
> > On Tue, Oct 14, 2014 at 8:18 AM, George Christman <
> gchrist...@cardaddy.com
> > wrote:
> > My original response still sta
Commented inline
On Tue, Oct 14, 2014 at 12:15 PM, Kalle Korhonen wrote:
> On Tue, Oct 14, 2014 at 8:18 AM, George Christman >
> wrote:
>
> > Geoff, I always try to follow you suggested pattern, but unfortunately I
> > don't think it's always possible. I'd like to present a use case scenario
>
I think you might be having the same issue I had a while ago [1]
Both the layout and the component are defined by the page. It's a bit
counter intuitive but the layout is not the component's parent so events
will not bubble up to it. The page is the parent to both.
[1]
http://apache-tapestry-mail
On Tue, Oct 14, 2014 at 8:18 AM, George Christman
wrote:
> Geoff, I always try to follow you suggested pattern, but unfortunately I
> don't think it's always possible. I'd like to present a use case scenario
> and perhaps maybe you guys can break me out of my current design rut.
> *Use case 1*
>
Does anybody using 5.4 understand this issue? I'm still unable to get
the clientside validation js working.
On Fri, Oct 10, 2014 at 1:59 PM, George Christman
wrote:
> I found one mistake where I wasn't calling the js directly from render,
> but that still doesn't seem to resolve the issue.
>
> @
Yup, that's exactly what was happening.
On Tue, Oct 14, 2014 at 11:35 AM, Lance Java
wrote:
> This makes sense. For validation errors, tapestry does NOT
> redirect-after-post so the POST request is the same as the render request.
> I can only assume that onPrepare() is called twice in the same r
This makes sense. For validation errors, tapestry does NOT
redirect-after-post so the POST request is the same as the render request.
I can only assume that onPrepare() is called twice in the same request in
the case of validation errors so your null check stops the POST values from
being overridde
Geoff, I always try to follow you suggested pattern, but unfortunately I
don't think it's always possible. I'd like to present a use case scenario
and perhaps maybe you guys can break me out of my current design rut.
*Use case 1*
1. My navigation bar is contained within my layout component which
I used to have a dummy zone in my layout component so I can use it's ID to
enable ajax for Select components if they aren't inside a zone and I can't
use "^" !!
> A good deal of the components already supports async parameter for exactly
>
> this.
Chris, so not *all* components does ? Should
Hi Nathan,
I've written a module which has support for multiple databases through
Hibernate. It's roughly based on Taha's implementation.
Besides that it contains a lot more usefull components ;)
See: https://github.com/intercommit/Weaves
Regards,
Antal
OriginalMessage
>From: "Nat
12 matches
Mail list logo