On Dec 9, 2005, at 11:39 AM, Chuck Hill wrote:
Um, "Ick!" is the first thing that comes to mind.
"Ick" is, as Arturo said, putting it mildly. I didn't come up with
this approach but I'm stuck with it now.
Thanks to you and everyone else who replied. I now have hope that
there truly is
On Dec 9, 2005, at 2:39 PM, Chuck Hill wrote:
HI Janine,
On Dec 8, 2005, at 10:49 PM, [EMAIL PROTECTED] wrote:
In my day job I build websites in a scripted environment. The
"conventional wisdom" on handling form validation errors goes like
this: the user goes to /foo and fills in the form
Hi, Janine,
As Chuck said, there are lots of ways of handling this. Perhaps the
following notes will make Chuck's first suggestion regarding
overriding validationFailedWithException in the WOComponent a little
more explicit. I took these notes from an article by Andrew Lindesay
in StepWis
HI Janine,
On Dec 8, 2005, at 10:49 PM, [EMAIL PROTECTED] wrote:
In my day job I build websites in a scripted environment. The
"conventional wisdom" on handling form validation errors goes like
this: the user goes to /foo and fills in the form. When they hit
the submit button, they are
[EMAIL PROTECTED] wrote:
In my day job I build websites in a scripted environment. The
"conventional wisdom" on handling form validation errors goes like
this: the user goes to /foo and fills in the form. When they hit the
submit button, they are routed back to /foo again, except this ti
In my day job I build websites in a scripted environment. The
"conventional wisdom" on handling form validation errors goes like
this: the user goes to /foo and fills in the form. When they hit
the submit button, they are routed back to /foo again, except this
time it's a POST instead of
