You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Marcelo Lotif <ml...@gmail.com> on 2007/12/28 19:29:02 UTC
T5.0.7 Validation error
When i switch to the 5.0.7 version, the validations of my BeanEditForms
doesn't work properly...
I have a BEF to add a user to the database. When i click on the submit
button, it must validate the fields and go to another page to show all the
users on the database. If there are errors on the validation, it must stay
at the same page and show the errors to the user (as expected). When i
switch to 5.0.7, even if i get some errors, the page goes to the another one
and the it ends up to add the user to the database with the errors. The
funny thing is when i come back to the page, the errors are there... If i
switch back to 5.0.6, everything works fine again.
Am i missing something or this is really an error?
--
Atenciosamente,
Marcelo Lotif
Re: T5.0.7 Validation error
Posted by Davor Hrg <hr...@gmail.com>.
isn't event name: validateForm
http://tapestry.formos.com/nightly/tapestry5/tapestry-core/ref/org/apache/tapestry/corelib/components/Form.html
under SubmitEvents topic
Davor Hrg
On Thu, Mar 6, 2008 at 4:56 PM, Joel Wiegman <Jo...@dswinc.com> wrote:
> componentResources.triggerEvent() appears to be broken in
> T5.0.11-SNAPSHOT
>
> I have the following situation:
>
> public class LayoutClass {
>
> @Component
> private Form editControlForm;
>
> public void onValidateFromEditControlForm() {
> resources.triggerEvent("formValidate", null, null);
> }
>
> }
>
> public class BaseClassThatUsesLayout {
>
> @Inject
> private LayoutClass layout;
>
> }
>
> public class SpecificPage extends BaseClassThatUsesLayout {
>
> public void onFormValidate() {
> System.out.println("Form validated!");
> }
>
> }
>
> When I upgraded from 5.0.7 to T5.0.11-SNAPSHOT the onFormValidate() is
> no longer called.
>
> Please advise... Thanks!
>
>
>
>
> -----Original Message-----
> From: Howard Lewis Ship [mailto:hlship@gmail.com]
>
>
> Sent: Friday, December 28, 2007 5:23 PM
> To: Tapestry users
> Subject: Re: T5.0.7 Validation error
>
> On Dec 28, 2007 1:44 PM, Joel Wiegman <Jo...@dswinc.com> wrote:
> > Ouch... That change botches up my current application pretty
> thoroughly.
> >
> > I don't think the event needs to be re-named... but consider the
> > following situation:
> >
> > If a form is in a layout component that other pages use via the
> > @Component annotation (say because most of the forms look very similar
>
> > and they want to re-use the presentation and validation logic), they
> > have no way of validating their forms in the pages, because they no
> > longer have access to the validate event from the form.
>
> You can do onValidateFromLayout() ... that is, if Form is inside Layout,
> then the event will bubble up from Layout to your page, and will appear
> to originate with Layout.
>
> Alternately, the Layout component could capture the Form's validate
> event and trigger a new event with a name of your choice:
>
> boolean onValidateFromForm()
> {
> _componentResources.trigger("layoutvalidate", null, null); }
>
> >
> > I tried using the onValidateFromIndividualField() technique... the
> > behavior of that seemed inconsistent (had to submit the form twice to
> > get the event to fire???).
>
> Huh?
>
> Are you sure your client-side validation wasn't preventing the form
> submission?
> >
> > How does one log these events to see which events are firing?
>
> That isn't really logged right now.
>
> >
> > Looks like I'll have to start validation over from ground zero if I
> > want to upgrade to 5.0.7...
> >
> > Perhaps the validation doc page could be updated with advice on proper
>
> > validation techniques?
> >
> >
> > -----Original Message-----
> > From: Howard Lewis Ship [mailto:hlship@gmail.com]
> >
> > Sent: Friday, December 28, 2007 3:25 PM
> > To: Tapestry users
> > Subject: Re: T5.0.7 Validation error
> >
> > Tapestry 5.0.7 adds a new way of validating input from the client, a
> > validate event that is emitted from individual components and is
> > distinct from the validate event from the form. The event handler
> > method you already had, that was intended for cross-form validation
> > after values are in place, is being executed too early, for each
> field.
> > Sorry, unexpected consequences. Perhaps the form's event should be
> > renamed from "validate" to "formValidate"?
> >
> > Change your method name from onValidate() to onValidateFromForm()
> > (adjusting for your form's id).
> >
> > On Dec 28, 2007 12:02 PM, Joel Wiegman <Jo...@dswinc.com> wrote:
> > > There appears to be a bug with 5.0.7 in that any custom validation
> > > method ( onValidate(), etc. ) gets called before the HTTP values get
>
> > > bound to the Tapestry component. Can anyone else confirm this?
> > >
> > > -----Original Message-----
> > > From: Joel Wiegman [mailto:JoelWiegman@dswinc.com]
> > > Sent: Friday, December 28, 2007 2:40 PM
> > > To: Tapestry users
> > >
> > > Subject: RE: T5.0.7 Validation error
> > >
> > > I'm trying to upgrade to 5.0.7 and can't get screens (that validated
>
> > > just fine with 5.0.6) to validate either.
> > >
> > > Will re-post once I find out more.
> > >
> > > -----Original Message-----
> > > From: Howard Lewis Ship [mailto:hlship@gmail.com]
> > > Sent: Friday, December 28, 2007 2:05 PM
> > > To: Tapestry users
> > > Subject: Re: T5.0.7 Validation error
> > >
> > > Try clearing your browser cache, you may have the old tapestry.js
> > > stuck in there.
> > >
> > > On Dec 28, 2007 10:29 AM, Marcelo Lotif <ml...@gmail.com>
> wrote:
> > > > When i switch to the 5.0.7 version, the validations of my
> > > > BeanEditForms doesn't work properly...
> > > > I have a BEF to add a user to the database. When i click on the
> > > > submit
> > >
> > > > button, it must validate the fields and go to another page to show
>
> > > > all
> > >
> > > > the users on the database. If there are errors on the validation,
> > > > it
> >
> > > > must stay at the same page and show the errors to the user (as
> > > > expected). When i switch to 5.0.7, even if i get some errors, the
> > > > page
> > >
> > > > goes to the another one and the it ends up to add the user to the
> > > > database with the errors. The funny thing is when i come back to
> > > > the
> >
> > > > page, the errors are there... If i switch back to 5.0.6,
> > > > everything
> > > works fine again.
> > > >
> > > > Am i missing something or this is really an error?
> > > >
> > > > --
> > > > Atenciosamente,
> > > > Marcelo Lotif
> > > >
> > >
> > >
> > >
> > > --
> > > Howard M. Lewis Ship
> > >
> > > Creator Apache Tapestry and Apache HiveMind
> > >
> > > --------------------------------------------------------------------
> > > - To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > For additional commands, e-mail: users-help@tapestry.apache.org
> > >
> > >
> > > --------------------------------------------------------------------
> > > - To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > For additional commands, e-mail: users-help@tapestry.apache.org
> > >
> > >
> > > --------------------------------------------------------------------
> > > - To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > For additional commands, e-mail: users-help@tapestry.apache.org
> > >
> > >
> >
> >
> >
> > --
> > Howard M. Lewis Ship
> >
> > Creator Apache Tapestry and Apache HiveMind
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
> >
>
>
>
> --
> Howard M. Lewis Ship
>
> Creator Apache Tapestry and Apache HiveMind
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
RE: T5.0.7 Validation error
Posted by Joel Wiegman <Jo...@dswinc.com>.
componentResources.triggerEvent() appears to be broken in
T5.0.11-SNAPSHOT
I have the following situation:
public class LayoutClass {
@Component
private Form editControlForm;
public void onValidateFromEditControlForm() {
resources.triggerEvent("formValidate", null, null);
}
}
public class BaseClassThatUsesLayout {
@Inject
private LayoutClass layout;
}
public class SpecificPage extends BaseClassThatUsesLayout {
public void onFormValidate() {
System.out.println("Form validated!");
}
}
When I upgraded from 5.0.7 to T5.0.11-SNAPSHOT the onFormValidate() is
no longer called.
Please advise... Thanks!
-----Original Message-----
From: Howard Lewis Ship [mailto:hlship@gmail.com]
Sent: Friday, December 28, 2007 5:23 PM
To: Tapestry users
Subject: Re: T5.0.7 Validation error
On Dec 28, 2007 1:44 PM, Joel Wiegman <Jo...@dswinc.com> wrote:
> Ouch... That change botches up my current application pretty
thoroughly.
>
> I don't think the event needs to be re-named... but consider the
> following situation:
>
> If a form is in a layout component that other pages use via the
> @Component annotation (say because most of the forms look very similar
> and they want to re-use the presentation and validation logic), they
> have no way of validating their forms in the pages, because they no
> longer have access to the validate event from the form.
You can do onValidateFromLayout() ... that is, if Form is inside Layout,
then the event will bubble up from Layout to your page, and will appear
to originate with Layout.
Alternately, the Layout component could capture the Form's validate
event and trigger a new event with a name of your choice:
boolean onValidateFromForm()
{
_componentResources.trigger("layoutvalidate", null, null); }
>
> I tried using the onValidateFromIndividualField() technique... the
> behavior of that seemed inconsistent (had to submit the form twice to
> get the event to fire???).
Huh?
Are you sure your client-side validation wasn't preventing the form
submission?
>
> How does one log these events to see which events are firing?
That isn't really logged right now.
>
> Looks like I'll have to start validation over from ground zero if I
> want to upgrade to 5.0.7...
>
> Perhaps the validation doc page could be updated with advice on proper
> validation techniques?
>
>
> -----Original Message-----
> From: Howard Lewis Ship [mailto:hlship@gmail.com]
>
> Sent: Friday, December 28, 2007 3:25 PM
> To: Tapestry users
> Subject: Re: T5.0.7 Validation error
>
> Tapestry 5.0.7 adds a new way of validating input from the client, a
> validate event that is emitted from individual components and is
> distinct from the validate event from the form. The event handler
> method you already had, that was intended for cross-form validation
> after values are in place, is being executed too early, for each
field.
> Sorry, unexpected consequences. Perhaps the form's event should be
> renamed from "validate" to "formValidate"?
>
> Change your method name from onValidate() to onValidateFromForm()
> (adjusting for your form's id).
>
> On Dec 28, 2007 12:02 PM, Joel Wiegman <Jo...@dswinc.com> wrote:
> > There appears to be a bug with 5.0.7 in that any custom validation
> > method ( onValidate(), etc. ) gets called before the HTTP values get
> > bound to the Tapestry component. Can anyone else confirm this?
> >
> > -----Original Message-----
> > From: Joel Wiegman [mailto:JoelWiegman@dswinc.com]
> > Sent: Friday, December 28, 2007 2:40 PM
> > To: Tapestry users
> >
> > Subject: RE: T5.0.7 Validation error
> >
> > I'm trying to upgrade to 5.0.7 and can't get screens (that validated
> > just fine with 5.0.6) to validate either.
> >
> > Will re-post once I find out more.
> >
> > -----Original Message-----
> > From: Howard Lewis Ship [mailto:hlship@gmail.com]
> > Sent: Friday, December 28, 2007 2:05 PM
> > To: Tapestry users
> > Subject: Re: T5.0.7 Validation error
> >
> > Try clearing your browser cache, you may have the old tapestry.js
> > stuck in there.
> >
> > On Dec 28, 2007 10:29 AM, Marcelo Lotif <ml...@gmail.com>
wrote:
> > > When i switch to the 5.0.7 version, the validations of my
> > > BeanEditForms doesn't work properly...
> > > I have a BEF to add a user to the database. When i click on the
> > > submit
> >
> > > button, it must validate the fields and go to another page to show
> > > all
> >
> > > the users on the database. If there are errors on the validation,
> > > it
>
> > > must stay at the same page and show the errors to the user (as
> > > expected). When i switch to 5.0.7, even if i get some errors, the
> > > page
> >
> > > goes to the another one and the it ends up to add the user to the
> > > database with the errors. The funny thing is when i come back to
> > > the
>
> > > page, the errors are there... If i switch back to 5.0.6,
> > > everything
> > works fine again.
> > >
> > > Am i missing something or this is really an error?
> > >
> > > --
> > > Atenciosamente,
> > > Marcelo Lotif
> > >
> >
> >
> >
> > --
> > Howard M. Lewis Ship
> >
> > Creator Apache Tapestry and Apache HiveMind
> >
> > --------------------------------------------------------------------
> > - To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
> >
> > --------------------------------------------------------------------
> > - To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
> >
> > --------------------------------------------------------------------
> > - To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
> >
>
>
>
> --
> Howard M. Lewis Ship
>
> Creator Apache Tapestry and Apache HiveMind
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
--
Howard M. Lewis Ship
Creator Apache Tapestry and Apache HiveMind
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
T5: Event order for "selected" and "validate" events
Posted by Joel Wiegman <Jo...@dswinc.com>.
All,
I've noticed that the "validate" event for a form fires before the
"selected" event fires from the Submit component.
IMHO, I think the "selected" event should fire first. Seems like I
would want to know HOW the form was submitted before I validate it (in
case I want to, say, skip validation on the form if a person clicks a
specific button).
Can anyone present a counter argument? If not I'll create a JIRA bug
(or is it a feature request?).
Cheers,
Joel
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: T5.0.7 Validation error
Posted by Marcelo Lotif <ml...@gmail.com>.
Fine...just clean the cache and the problem is gone
unless for IE6, the bubbles are totally messed up there...
2007/12/29, dwi ardi irawan < penyihirkecil@gmail.com>:
>
> oops...already fixed.
> delete the cookies like howard said.
>
> On Dec 29, 2007 1:30 PM, dwi ardi irawan <pe...@gmail.com> wrote:
>
> > I got this error when i updated my app into t5.0.7
> > java.lang.NoClassDefFoundError org/apache/tapestry/beaneditor/Validate
> >
> > doesy anybody know how to fix it ?
> >
> >
> > On Dec 29, 2007 5:23 AM, Howard Lewis Ship < hlship@gmail.com> wrote:
> >
> > > On Dec 28, 2007 1:44 PM, Joel Wiegman < JoelWiegman@dswinc.com> wrote:
> > > > Ouch... That change botches up my current application pretty
> > > thoroughly.
> > > >
> > > > I don't think the event needs to be re-named... but consider the
> > > > following situation:
> > > >
> > > > If a form is in a layout component that other pages use via the
> > > > @Component annotation (say because most of the forms look very
> similar
> > > > and they want to re-use the presentation and validation logic), they
> > > > have no way of validating their forms in the pages, because they no
> > > > longer have access to the validate event from the form.
> > >
> > > You can do onValidateFromLayout() ... that is, if Form is inside
> > > Layout, then the event will bubble up from Layout to your page, and
> > > will appear to originate with Layout.
> > >
> > > Alternately, the Layout component could capture the Form's validate
> > > event and trigger a new event with a name of your choice:
> > >
> > > boolean onValidateFromForm()
> > > {
> > > _componentResources.trigger("layoutvalidate", null, null);
> > > }
> > >
> > > >
> > > > I tried using the onValidateFromIndividualField() technique... the
> > > > behavior of that seemed inconsistent (had to submit the form twice
> to
> > > > get the event to fire???).
> > >
> > > Huh?
> > >
> > > Are you sure your client-side validation wasn't preventing the form
> > > submission?
> > > >
> > > > How does one log these events to see which events are firing?
> > >
> > > That isn't really logged right now.
> > >
> > > >
> > > > Looks like I'll have to start validation over from ground zero if I
> > > want
> > > > to upgrade to 5.0.7...
> > > >
> > > > Perhaps the validation doc page could be updated with advice on
> proper
> > > > validation techniques?
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: Howard Lewis Ship [mailto: hlship@gmail.com ]
> > > >
> > > > Sent: Friday, December 28, 2007 3:25 PM
> > > > To: Tapestry users
> > > > Subject: Re: T5.0.7 Validation error
> > > >
> > > > Tapestry 5.0.7 adds a new way of validating input from the client, a
> > > > validate event that is emitted from individual components and is
> > > > distinct from the validate event from the form. The event handler
> > > method
> > > > you already had, that was intended for cross-form validation after
> > > > values are in place, is being executed too early, for each field.
> > > > Sorry, unexpected consequences. Perhaps the form's event should be
> > > > renamed from "validate" to "formValidate"?
> > > >
> > > > Change your method name from onValidate() to onValidateFromForm()
> > > > (adjusting for your form's id).
> > > >
> > > > On Dec 28, 2007 12:02 PM, Joel Wiegman < JoelWiegman@dswinc.com>
> > > wrote:
> > > > > There appears to be a bug with 5.0.7 in that any custom validation
> > > > > method ( onValidate(), etc. ) gets called before the HTTP values
> get
> > > > > bound to the Tapestry component. Can anyone else confirm this?
> > > > >
> > > > > -----Original Message-----
> > > > > From: Joel Wiegman [mailto:JoelWiegman@dswinc.com]
> > > > > Sent: Friday, December 28, 2007 2:40 PM
> > > > > To: Tapestry users
> > > > >
> > > > > Subject: RE: T5.0.7 Validation error
> > > > >
> > > > > I'm trying to upgrade to 5.0.7 and can't get screens (that
> validated
> > > > > just fine with 5.0.6) to validate either.
> > > > >
> > > > > Will re-post once I find out more.
> > > > >
> > > > > -----Original Message-----
> > > > > From: Howard Lewis Ship [mailto:hlship@gmail.com]
> > > > > Sent: Friday, December 28, 2007 2:05 PM
> > > > > To: Tapestry users
> > > > > Subject: Re: T5.0.7 Validation error
> > > > >
> > > > > Try clearing your browser cache, you may have the old tapestry.js
> > > > > stuck in there.
> > > > >
> > > > > On Dec 28, 2007 10:29 AM, Marcelo Lotif < mlotifjava@gmail.com>
> > > wrote:
> > > > > > When i switch to the 5.0.7 version, the validations of my
> > > > > > BeanEditForms doesn't work properly...
> > > > > > I have a BEF to add a user to the database. When i click on the
> > > > > > submit
> > > > >
> > > > > > button, it must validate the fields and go to another page to
> show
> > > > > > all
> > > > >
> > > > > > the users on the database. If there are errors on the
> validation,
> > > it
> > > >
> > > > > > must stay at the same page and show the errors to the user (as
> > > > > > expected). When i switch to 5.0.7, even if i get some errors,
> the
> > > > > > page
> > > > >
> > > > > > goes to the another one and the it ends up to add the user to
> the
> > > > > > database with the errors. The funny thing is when i come back to
> > > the
> > > >
> > > > > > page, the errors are there... If i switch back to 5.0.6,
> > > everything
> > > > > works fine again.
> > > > > >
> > > > > > Am i missing something or this is really an error?
> > > > > >
> > > > > > --
> > > > > > Atenciosamente,
> > > > > > Marcelo Lotif
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Howard M. Lewis Ship
> > > > >
> > > > > Creator Apache Tapestry and Apache HiveMind
> > > > >
> > > > >
> > > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > > > For additional commands, e-mail: users-help@tapestry.apache.org
> > > > >
> > > > >
> > > > >
> > > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > > > For additional commands, e-mail: users-help@tapestry.apache.org
> > > > >
> > > > >
> > > > >
> > > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > > > For additional commands, e-mail: users-help@tapestry.apache.org
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Howard M. Lewis Ship
> > > >
> > > > Creator Apache Tapestry and Apache HiveMind
> > > >
> > > >
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > > For additional commands, e-mail: users-help@tapestry.apache.org
> > > >
> > > >
> > > >
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > > For additional commands, e-mail: users-help@tapestry.apache.org
> > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Howard M. Lewis Ship
> > >
> > > Creator Apache Tapestry and Apache HiveMind
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > For additional commands, e-mail: users-help@tapestry.apache.org
> > >
> > >
> >
> >
> > --
> > http://dwiardiirawan.blogspot.com
> > "cos everyone could be extraordinary...lighten up !"
> >
>
>
>
> --
> http://dwiardiirawan.blogspot.com
> "cos everyone could be extraordinary...lighten up !"
>
--
Atenciosamente,
Marcelo Lotif
Re: T5.0.7 Validation error
Posted by dwi ardi irawan <pe...@gmail.com>.
oops...already fixed.
delete the cookies like howard said.
On Dec 29, 2007 1:30 PM, dwi ardi irawan <pe...@gmail.com> wrote:
> I got this error when i updated my app into t5.0.7
> java.lang.NoClassDefFoundError org/apache/tapestry/beaneditor/Validate
>
> doesy anybody know how to fix it ?
>
>
> On Dec 29, 2007 5:23 AM, Howard Lewis Ship < hlship@gmail.com> wrote:
>
> > On Dec 28, 2007 1:44 PM, Joel Wiegman < JoelWiegman@dswinc.com> wrote:
> > > Ouch... That change botches up my current application pretty
> > thoroughly.
> > >
> > > I don't think the event needs to be re-named... but consider the
> > > following situation:
> > >
> > > If a form is in a layout component that other pages use via the
> > > @Component annotation (say because most of the forms look very similar
> > > and they want to re-use the presentation and validation logic), they
> > > have no way of validating their forms in the pages, because they no
> > > longer have access to the validate event from the form.
> >
> > You can do onValidateFromLayout() ... that is, if Form is inside
> > Layout, then the event will bubble up from Layout to your page, and
> > will appear to originate with Layout.
> >
> > Alternately, the Layout component could capture the Form's validate
> > event and trigger a new event with a name of your choice:
> >
> > boolean onValidateFromForm()
> > {
> > _componentResources.trigger("layoutvalidate", null, null);
> > }
> >
> > >
> > > I tried using the onValidateFromIndividualField() technique... the
> > > behavior of that seemed inconsistent (had to submit the form twice to
> > > get the event to fire???).
> >
> > Huh?
> >
> > Are you sure your client-side validation wasn't preventing the form
> > submission?
> > >
> > > How does one log these events to see which events are firing?
> >
> > That isn't really logged right now.
> >
> > >
> > > Looks like I'll have to start validation over from ground zero if I
> > want
> > > to upgrade to 5.0.7...
> > >
> > > Perhaps the validation doc page could be updated with advice on proper
> > > validation techniques?
> > >
> > >
> > > -----Original Message-----
> > > From: Howard Lewis Ship [mailto: hlship@gmail.com]
> > >
> > > Sent: Friday, December 28, 2007 3:25 PM
> > > To: Tapestry users
> > > Subject: Re: T5.0.7 Validation error
> > >
> > > Tapestry 5.0.7 adds a new way of validating input from the client, a
> > > validate event that is emitted from individual components and is
> > > distinct from the validate event from the form. The event handler
> > method
> > > you already had, that was intended for cross-form validation after
> > > values are in place, is being executed too early, for each field.
> > > Sorry, unexpected consequences. Perhaps the form's event should be
> > > renamed from "validate" to "formValidate"?
> > >
> > > Change your method name from onValidate() to onValidateFromForm()
> > > (adjusting for your form's id).
> > >
> > > On Dec 28, 2007 12:02 PM, Joel Wiegman < JoelWiegman@dswinc.com>
> > wrote:
> > > > There appears to be a bug with 5.0.7 in that any custom validation
> > > > method ( onValidate(), etc. ) gets called before the HTTP values get
> > > > bound to the Tapestry component. Can anyone else confirm this?
> > > >
> > > > -----Original Message-----
> > > > From: Joel Wiegman [mailto:JoelWiegman@dswinc.com]
> > > > Sent: Friday, December 28, 2007 2:40 PM
> > > > To: Tapestry users
> > > >
> > > > Subject: RE: T5.0.7 Validation error
> > > >
> > > > I'm trying to upgrade to 5.0.7 and can't get screens (that validated
> > > > just fine with 5.0.6) to validate either.
> > > >
> > > > Will re-post once I find out more.
> > > >
> > > > -----Original Message-----
> > > > From: Howard Lewis Ship [mailto:hlship@gmail.com]
> > > > Sent: Friday, December 28, 2007 2:05 PM
> > > > To: Tapestry users
> > > > Subject: Re: T5.0.7 Validation error
> > > >
> > > > Try clearing your browser cache, you may have the old tapestry.js
> > > > stuck in there.
> > > >
> > > > On Dec 28, 2007 10:29 AM, Marcelo Lotif < mlotifjava@gmail.com>
> > wrote:
> > > > > When i switch to the 5.0.7 version, the validations of my
> > > > > BeanEditForms doesn't work properly...
> > > > > I have a BEF to add a user to the database. When i click on the
> > > > > submit
> > > >
> > > > > button, it must validate the fields and go to another page to show
> > > > > all
> > > >
> > > > > the users on the database. If there are errors on the validation,
> > it
> > >
> > > > > must stay at the same page and show the errors to the user (as
> > > > > expected). When i switch to 5.0.7, even if i get some errors, the
> > > > > page
> > > >
> > > > > goes to the another one and the it ends up to add the user to the
> > > > > database with the errors. The funny thing is when i come back to
> > the
> > >
> > > > > page, the errors are there... If i switch back to 5.0.6,
> > everything
> > > > works fine again.
> > > > >
> > > > > Am i missing something or this is really an error?
> > > > >
> > > > > --
> > > > > Atenciosamente,
> > > > > Marcelo Lotif
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Howard M. Lewis Ship
> > > >
> > > > Creator Apache Tapestry and Apache HiveMind
> > > >
> > > >
> > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > > For additional commands, e-mail: users-help@tapestry.apache.org
> > > >
> > > >
> > > >
> > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > > For additional commands, e-mail: users-help@tapestry.apache.org
> > > >
> > > >
> > > >
> > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > > For additional commands, e-mail: users-help@tapestry.apache.org
> > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Howard M. Lewis Ship
> > >
> > > Creator Apache Tapestry and Apache HiveMind
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > For additional commands, e-mail: users-help@tapestry.apache.org
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > For additional commands, e-mail: users-help@tapestry.apache.org
> > >
> > >
> >
> >
> >
> > --
> > Howard M. Lewis Ship
> >
> > Creator Apache Tapestry and Apache HiveMind
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
> >
>
>
> --
> http://dwiardiirawan.blogspot.com
> "cos everyone could be extraordinary...lighten up !"
>
--
http://dwiardiirawan.blogspot.com
"cos everyone could be extraordinary...lighten up !"
Re: T5.0.7 Validation error
Posted by dwi ardi irawan <pe...@gmail.com>.
I got this error when i updated my app into t5.0.7
java.lang.NoClassDefFoundError org/apache/tapestry/beaneditor/Validate
doesy anybody know how to fix it ?
On Dec 29, 2007 5:23 AM, Howard Lewis Ship <hl...@gmail.com> wrote:
> On Dec 28, 2007 1:44 PM, Joel Wiegman <Jo...@dswinc.com> wrote:
> > Ouch... That change botches up my current application pretty thoroughly.
> >
> > I don't think the event needs to be re-named... but consider the
> > following situation:
> >
> > If a form is in a layout component that other pages use via the
> > @Component annotation (say because most of the forms look very similar
> > and they want to re-use the presentation and validation logic), they
> > have no way of validating their forms in the pages, because they no
> > longer have access to the validate event from the form.
>
> You can do onValidateFromLayout() ... that is, if Form is inside
> Layout, then the event will bubble up from Layout to your page, and
> will appear to originate with Layout.
>
> Alternately, the Layout component could capture the Form's validate
> event and trigger a new event with a name of your choice:
>
> boolean onValidateFromForm()
> {
> _componentResources.trigger("layoutvalidate", null, null);
> }
>
> >
> > I tried using the onValidateFromIndividualField() technique... the
> > behavior of that seemed inconsistent (had to submit the form twice to
> > get the event to fire???).
>
> Huh?
>
> Are you sure your client-side validation wasn't preventing the form
> submission?
> >
> > How does one log these events to see which events are firing?
>
> That isn't really logged right now.
>
> >
> > Looks like I'll have to start validation over from ground zero if I want
> > to upgrade to 5.0.7...
> >
> > Perhaps the validation doc page could be updated with advice on proper
> > validation techniques?
> >
> >
> > -----Original Message-----
> > From: Howard Lewis Ship [mailto:hlship@gmail.com]
> >
> > Sent: Friday, December 28, 2007 3:25 PM
> > To: Tapestry users
> > Subject: Re: T5.0.7 Validation error
> >
> > Tapestry 5.0.7 adds a new way of validating input from the client, a
> > validate event that is emitted from individual components and is
> > distinct from the validate event from the form. The event handler method
> > you already had, that was intended for cross-form validation after
> > values are in place, is being executed too early, for each field.
> > Sorry, unexpected consequences. Perhaps the form's event should be
> > renamed from "validate" to "formValidate"?
> >
> > Change your method name from onValidate() to onValidateFromForm()
> > (adjusting for your form's id).
> >
> > On Dec 28, 2007 12:02 PM, Joel Wiegman <Jo...@dswinc.com> wrote:
> > > There appears to be a bug with 5.0.7 in that any custom validation
> > > method ( onValidate(), etc. ) gets called before the HTTP values get
> > > bound to the Tapestry component. Can anyone else confirm this?
> > >
> > > -----Original Message-----
> > > From: Joel Wiegman [mailto:JoelWiegman@dswinc.com]
> > > Sent: Friday, December 28, 2007 2:40 PM
> > > To: Tapestry users
> > >
> > > Subject: RE: T5.0.7 Validation error
> > >
> > > I'm trying to upgrade to 5.0.7 and can't get screens (that validated
> > > just fine with 5.0.6) to validate either.
> > >
> > > Will re-post once I find out more.
> > >
> > > -----Original Message-----
> > > From: Howard Lewis Ship [mailto:hlship@gmail.com]
> > > Sent: Friday, December 28, 2007 2:05 PM
> > > To: Tapestry users
> > > Subject: Re: T5.0.7 Validation error
> > >
> > > Try clearing your browser cache, you may have the old tapestry.js
> > > stuck in there.
> > >
> > > On Dec 28, 2007 10:29 AM, Marcelo Lotif <ml...@gmail.com> wrote:
> > > > When i switch to the 5.0.7 version, the validations of my
> > > > BeanEditForms doesn't work properly...
> > > > I have a BEF to add a user to the database. When i click on the
> > > > submit
> > >
> > > > button, it must validate the fields and go to another page to show
> > > > all
> > >
> > > > the users on the database. If there are errors on the validation, it
> >
> > > > must stay at the same page and show the errors to the user (as
> > > > expected). When i switch to 5.0.7, even if i get some errors, the
> > > > page
> > >
> > > > goes to the another one and the it ends up to add the user to the
> > > > database with the errors. The funny thing is when i come back to the
> >
> > > > page, the errors are there... If i switch back to 5.0.6, everything
> > > works fine again.
> > > >
> > > > Am i missing something or this is really an error?
> > > >
> > > > --
> > > > Atenciosamente,
> > > > Marcelo Lotif
> > > >
> > >
> > >
> > >
> > > --
> > > Howard M. Lewis Ship
> > >
> > > Creator Apache Tapestry and Apache HiveMind
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > For additional commands, e-mail: users-help@tapestry.apache.org
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > For additional commands, e-mail: users-help@tapestry.apache.org
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > > For additional commands, e-mail: users-help@tapestry.apache.org
> > >
> > >
> >
> >
> >
> > --
> > Howard M. Lewis Ship
> >
> > Creator Apache Tapestry and Apache HiveMind
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
> >
>
>
>
> --
> Howard M. Lewis Ship
>
> Creator Apache Tapestry and Apache HiveMind
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
--
http://dwiardiirawan.blogspot.com
"cos everyone could be extraordinary...lighten up !"
Re: T5.0.7 Validation error
Posted by Howard Lewis Ship <hl...@gmail.com>.
On Dec 28, 2007 1:44 PM, Joel Wiegman <Jo...@dswinc.com> wrote:
> Ouch... That change botches up my current application pretty thoroughly.
>
> I don't think the event needs to be re-named... but consider the
> following situation:
>
> If a form is in a layout component that other pages use via the
> @Component annotation (say because most of the forms look very similar
> and they want to re-use the presentation and validation logic), they
> have no way of validating their forms in the pages, because they no
> longer have access to the validate event from the form.
You can do onValidateFromLayout() ... that is, if Form is inside
Layout, then the event will bubble up from Layout to your page, and
will appear to originate with Layout.
Alternately, the Layout component could capture the Form's validate
event and trigger a new event with a name of your choice:
boolean onValidateFromForm()
{
_componentResources.trigger("layoutvalidate", null, null);
}
>
> I tried using the onValidateFromIndividualField() technique... the
> behavior of that seemed inconsistent (had to submit the form twice to
> get the event to fire???).
Huh?
Are you sure your client-side validation wasn't preventing the form submission?
>
> How does one log these events to see which events are firing?
That isn't really logged right now.
>
> Looks like I'll have to start validation over from ground zero if I want
> to upgrade to 5.0.7...
>
> Perhaps the validation doc page could be updated with advice on proper
> validation techniques?
>
>
> -----Original Message-----
> From: Howard Lewis Ship [mailto:hlship@gmail.com]
>
> Sent: Friday, December 28, 2007 3:25 PM
> To: Tapestry users
> Subject: Re: T5.0.7 Validation error
>
> Tapestry 5.0.7 adds a new way of validating input from the client, a
> validate event that is emitted from individual components and is
> distinct from the validate event from the form. The event handler method
> you already had, that was intended for cross-form validation after
> values are in place, is being executed too early, for each field.
> Sorry, unexpected consequences. Perhaps the form's event should be
> renamed from "validate" to "formValidate"?
>
> Change your method name from onValidate() to onValidateFromForm()
> (adjusting for your form's id).
>
> On Dec 28, 2007 12:02 PM, Joel Wiegman <Jo...@dswinc.com> wrote:
> > There appears to be a bug with 5.0.7 in that any custom validation
> > method ( onValidate(), etc. ) gets called before the HTTP values get
> > bound to the Tapestry component. Can anyone else confirm this?
> >
> > -----Original Message-----
> > From: Joel Wiegman [mailto:JoelWiegman@dswinc.com]
> > Sent: Friday, December 28, 2007 2:40 PM
> > To: Tapestry users
> >
> > Subject: RE: T5.0.7 Validation error
> >
> > I'm trying to upgrade to 5.0.7 and can't get screens (that validated
> > just fine with 5.0.6) to validate either.
> >
> > Will re-post once I find out more.
> >
> > -----Original Message-----
> > From: Howard Lewis Ship [mailto:hlship@gmail.com]
> > Sent: Friday, December 28, 2007 2:05 PM
> > To: Tapestry users
> > Subject: Re: T5.0.7 Validation error
> >
> > Try clearing your browser cache, you may have the old tapestry.js
> > stuck in there.
> >
> > On Dec 28, 2007 10:29 AM, Marcelo Lotif <ml...@gmail.com> wrote:
> > > When i switch to the 5.0.7 version, the validations of my
> > > BeanEditForms doesn't work properly...
> > > I have a BEF to add a user to the database. When i click on the
> > > submit
> >
> > > button, it must validate the fields and go to another page to show
> > > all
> >
> > > the users on the database. If there are errors on the validation, it
>
> > > must stay at the same page and show the errors to the user (as
> > > expected). When i switch to 5.0.7, even if i get some errors, the
> > > page
> >
> > > goes to the another one and the it ends up to add the user to the
> > > database with the errors. The funny thing is when i come back to the
>
> > > page, the errors are there... If i switch back to 5.0.6, everything
> > works fine again.
> > >
> > > Am i missing something or this is really an error?
> > >
> > > --
> > > Atenciosamente,
> > > Marcelo Lotif
> > >
> >
> >
> >
> > --
> > Howard M. Lewis Ship
> >
> > Creator Apache Tapestry and Apache HiveMind
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
> >
>
>
>
> --
> Howard M. Lewis Ship
>
> Creator Apache Tapestry and Apache HiveMind
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
--
Howard M. Lewis Ship
Creator Apache Tapestry and Apache HiveMind
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
RE: T5.0.7 Validation error
Posted by Joel Wiegman <Jo...@dswinc.com>.
Ouch... That change botches up my current application pretty thoroughly.
I don't think the event needs to be re-named... but consider the
following situation:
If a form is in a layout component that other pages use via the
@Component annotation (say because most of the forms look very similar
and they want to re-use the presentation and validation logic), they
have no way of validating their forms in the pages, because they no
longer have access to the validate event from the form.
I tried using the onValidateFromIndividualField() technique... the
behavior of that seemed inconsistent (had to submit the form twice to
get the event to fire???).
How does one log these events to see which events are firing?
Looks like I'll have to start validation over from ground zero if I want
to upgrade to 5.0.7...
Perhaps the validation doc page could be updated with advice on proper
validation techniques?
-----Original Message-----
From: Howard Lewis Ship [mailto:hlship@gmail.com]
Sent: Friday, December 28, 2007 3:25 PM
To: Tapestry users
Subject: Re: T5.0.7 Validation error
Tapestry 5.0.7 adds a new way of validating input from the client, a
validate event that is emitted from individual components and is
distinct from the validate event from the form. The event handler method
you already had, that was intended for cross-form validation after
values are in place, is being executed too early, for each field.
Sorry, unexpected consequences. Perhaps the form's event should be
renamed from "validate" to "formValidate"?
Change your method name from onValidate() to onValidateFromForm()
(adjusting for your form's id).
On Dec 28, 2007 12:02 PM, Joel Wiegman <Jo...@dswinc.com> wrote:
> There appears to be a bug with 5.0.7 in that any custom validation
> method ( onValidate(), etc. ) gets called before the HTTP values get
> bound to the Tapestry component. Can anyone else confirm this?
>
> -----Original Message-----
> From: Joel Wiegman [mailto:JoelWiegman@dswinc.com]
> Sent: Friday, December 28, 2007 2:40 PM
> To: Tapestry users
>
> Subject: RE: T5.0.7 Validation error
>
> I'm trying to upgrade to 5.0.7 and can't get screens (that validated
> just fine with 5.0.6) to validate either.
>
> Will re-post once I find out more.
>
> -----Original Message-----
> From: Howard Lewis Ship [mailto:hlship@gmail.com]
> Sent: Friday, December 28, 2007 2:05 PM
> To: Tapestry users
> Subject: Re: T5.0.7 Validation error
>
> Try clearing your browser cache, you may have the old tapestry.js
> stuck in there.
>
> On Dec 28, 2007 10:29 AM, Marcelo Lotif <ml...@gmail.com> wrote:
> > When i switch to the 5.0.7 version, the validations of my
> > BeanEditForms doesn't work properly...
> > I have a BEF to add a user to the database. When i click on the
> > submit
>
> > button, it must validate the fields and go to another page to show
> > all
>
> > the users on the database. If there are errors on the validation, it
> > must stay at the same page and show the errors to the user (as
> > expected). When i switch to 5.0.7, even if i get some errors, the
> > page
>
> > goes to the another one and the it ends up to add the user to the
> > database with the errors. The funny thing is when i come back to the
> > page, the errors are there... If i switch back to 5.0.6, everything
> works fine again.
> >
> > Am i missing something or this is really an error?
> >
> > --
> > Atenciosamente,
> > Marcelo Lotif
> >
>
>
>
> --
> Howard M. Lewis Ship
>
> Creator Apache Tapestry and Apache HiveMind
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
--
Howard M. Lewis Ship
Creator Apache Tapestry and Apache HiveMind
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: T5.0.7 Validation error
Posted by Howard Lewis Ship <hl...@gmail.com>.
Tapestry 5.0.7 adds a new way of validating input from the client, a
validate event that is emitted from individual components and is
distinct from the validate event from the form. The event handler
method you already had, that was intended for cross-form validation
after values are in place, is being executed too early, for each
field. Sorry, unexpected consequences. Perhaps the form's event
should be renamed from "validate" to "formValidate"?
Change your method name from onValidate() to onValidateFromForm()
(adjusting for your form's id).
On Dec 28, 2007 12:02 PM, Joel Wiegman <Jo...@dswinc.com> wrote:
> There appears to be a bug with 5.0.7 in that any custom validation
> method ( onValidate(), etc. ) gets called before the HTTP values get
> bound to the Tapestry component. Can anyone else confirm this?
>
> -----Original Message-----
> From: Joel Wiegman [mailto:JoelWiegman@dswinc.com]
> Sent: Friday, December 28, 2007 2:40 PM
> To: Tapestry users
>
> Subject: RE: T5.0.7 Validation error
>
> I'm trying to upgrade to 5.0.7 and can't get screens (that validated
> just fine with 5.0.6) to validate either.
>
> Will re-post once I find out more.
>
> -----Original Message-----
> From: Howard Lewis Ship [mailto:hlship@gmail.com]
> Sent: Friday, December 28, 2007 2:05 PM
> To: Tapestry users
> Subject: Re: T5.0.7 Validation error
>
> Try clearing your browser cache, you may have the old tapestry.js stuck
> in there.
>
> On Dec 28, 2007 10:29 AM, Marcelo Lotif <ml...@gmail.com> wrote:
> > When i switch to the 5.0.7 version, the validations of my
> > BeanEditForms doesn't work properly...
> > I have a BEF to add a user to the database. When i click on the submit
>
> > button, it must validate the fields and go to another page to show all
>
> > the users on the database. If there are errors on the validation, it
> > must stay at the same page and show the errors to the user (as
> > expected). When i switch to 5.0.7, even if i get some errors, the page
>
> > goes to the another one and the it ends up to add the user to the
> > database with the errors. The funny thing is when i come back to the
> > page, the errors are there... If i switch back to 5.0.6, everything
> works fine again.
> >
> > Am i missing something or this is really an error?
> >
> > --
> > Atenciosamente,
> > Marcelo Lotif
> >
>
>
>
> --
> Howard M. Lewis Ship
>
> Creator Apache Tapestry and Apache HiveMind
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
--
Howard M. Lewis Ship
Creator Apache Tapestry and Apache HiveMind
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
RE: T5.0.7 Validation error
Posted by Joel Wiegman <Jo...@dswinc.com>.
There appears to be a bug with 5.0.7 in that any custom validation
method ( onValidate(), etc. ) gets called before the HTTP values get
bound to the Tapestry component. Can anyone else confirm this?
-----Original Message-----
From: Joel Wiegman [mailto:JoelWiegman@dswinc.com]
Sent: Friday, December 28, 2007 2:40 PM
To: Tapestry users
Subject: RE: T5.0.7 Validation error
I'm trying to upgrade to 5.0.7 and can't get screens (that validated
just fine with 5.0.6) to validate either.
Will re-post once I find out more.
-----Original Message-----
From: Howard Lewis Ship [mailto:hlship@gmail.com]
Sent: Friday, December 28, 2007 2:05 PM
To: Tapestry users
Subject: Re: T5.0.7 Validation error
Try clearing your browser cache, you may have the old tapestry.js stuck
in there.
On Dec 28, 2007 10:29 AM, Marcelo Lotif <ml...@gmail.com> wrote:
> When i switch to the 5.0.7 version, the validations of my
> BeanEditForms doesn't work properly...
> I have a BEF to add a user to the database. When i click on the submit
> button, it must validate the fields and go to another page to show all
> the users on the database. If there are errors on the validation, it
> must stay at the same page and show the errors to the user (as
> expected). When i switch to 5.0.7, even if i get some errors, the page
> goes to the another one and the it ends up to add the user to the
> database with the errors. The funny thing is when i come back to the
> page, the errors are there... If i switch back to 5.0.6, everything
works fine again.
>
> Am i missing something or this is really an error?
>
> --
> Atenciosamente,
> Marcelo Lotif
>
--
Howard M. Lewis Ship
Creator Apache Tapestry and Apache HiveMind
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
RE: T5.0.7 Validation error
Posted by Joel Wiegman <Jo...@dswinc.com>.
I'm trying to upgrade to 5.0.7 and can't get screens (that validated
just fine with 5.0.6) to validate either.
Will re-post once I find out more.
-----Original Message-----
From: Howard Lewis Ship [mailto:hlship@gmail.com]
Sent: Friday, December 28, 2007 2:05 PM
To: Tapestry users
Subject: Re: T5.0.7 Validation error
Try clearing your browser cache, you may have the old tapestry.js stuck
in there.
On Dec 28, 2007 10:29 AM, Marcelo Lotif <ml...@gmail.com> wrote:
> When i switch to the 5.0.7 version, the validations of my
> BeanEditForms doesn't work properly...
> I have a BEF to add a user to the database. When i click on the submit
> button, it must validate the fields and go to another page to show all
> the users on the database. If there are errors on the validation, it
> must stay at the same page and show the errors to the user (as
> expected). When i switch to 5.0.7, even if i get some errors, the page
> goes to the another one and the it ends up to add the user to the
> database with the errors. The funny thing is when i come back to the
> page, the errors are there... If i switch back to 5.0.6, everything
works fine again.
>
> Am i missing something or this is really an error?
>
> --
> Atenciosamente,
> Marcelo Lotif
>
--
Howard M. Lewis Ship
Creator Apache Tapestry and Apache HiveMind
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: T5.0.7 Validation error
Posted by Howard Lewis Ship <hl...@gmail.com>.
Try clearing your browser cache, you may have the old tapestry.js
stuck in there.
On Dec 28, 2007 10:29 AM, Marcelo Lotif <ml...@gmail.com> wrote:
> When i switch to the 5.0.7 version, the validations of my BeanEditForms
> doesn't work properly...
> I have a BEF to add a user to the database. When i click on the submit
> button, it must validate the fields and go to another page to show all the
> users on the database. If there are errors on the validation, it must stay
> at the same page and show the errors to the user (as expected). When i
> switch to 5.0.7, even if i get some errors, the page goes to the another one
> and the it ends up to add the user to the database with the errors. The
> funny thing is when i come back to the page, the errors are there... If i
> switch back to 5.0.6, everything works fine again.
>
> Am i missing something or this is really an error?
>
> --
> Atenciosamente,
> Marcelo Lotif
>
--
Howard M. Lewis Ship
Creator Apache Tapestry and Apache HiveMind
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org