Issue created: https://issues.apache.org/jira/browse/TAP5-1393.
I'll provide some attachments that show a scenario where the bug happens (basically the same code that I put on the e-mail I previously sent to the list). Thanks for your time, Thiago. Atenciosamente, Matheus Eduardo Machado Moreira matheus....@gmail.com *Good cooking takes time. If you are made to wait, it is to serve you better, and to please you.* Menu do Restaurant Antoine, New Orleans 2010/12/28 Thiago H. de Paula Figueiredo <thiag...@gmail.com> > On Tue, 28 Dec 2010 13:55:06 -0200, Matheus Eduardo Machado Moreira < > matheus....@gmail.com> wrote: > > Reading the Form component class (beginRender() method) I found that a >> BeanValidationContextImpl is pushed into the Environment before >> "prepareForRender" and "prepare" events are triggered. I could handle the >> problem combining the code of the methods onActivate() and >> prepararFormulario() on the method onActivate(). Yet I think that the >> situation represents a bug and maybe it is simple to correct - just >> move *environment.push(BeanValidationContext.class, >> new BeanValidationContextImpl(validate));* (Form.class line 393) below >> *resources.triggerEvent(EventConstants.PREPARE, >> context, null);* (Form.class line 408). >> > > This looks like a bug. Please file a ticket at the > tapestry-beans-validation project at JIRA. > > -- > Thiago H. de Paula Figueiredo > Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, > and instructor > Owner, Ars Machina Tecnologia da Informação Ltda. > http://www.arsmachina.com.br > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
