Re: [5.2.4] Bean Validation integration - another possible bug
Igor Drobiazko, I'm glad to know that you fixed the issue I filled. It was quick! Thank you very much! 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 Matheus Eduardo Machado Moreira matheus@gmail.com 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
[5.2.4] Bean Validation integration - another possible bug
Hello again. Just found another possible bug in the Bean Validation integration. See the error stack trace: 2010-12-28 13:18:40,983 [btpool0-1] ERROR tapestry.render.br.com.eteg.cromoup.pages.acesso.EditarPermissao - Render queue error in BeginRender[acesso/EditarPermissao:nome]: Class cannot be null org.apache.tapestry5.ioc.internal.util.TapestryException: Class cannot be null [at classpath:br/com/eteg/cromoup/pages/acesso/EditarPermissao.tml, line 19] at org.apache.tapestry5.internal.structure.ComponentPageElementImpl$AbstractPhase.invoke(ComponentPageElementImpl.java:194) at org.apache.tapestry5.internal.structure.ComponentPageElementImpl$BeginRenderPhase.render(ComponentPageElementImpl.java:246) at org.apache.tapestry5.internal.services.RenderQueueImpl.run(RenderQueueImpl.java:72) at org.apache.tapestry5.internal.services.PageRenderQueueImpl.render(PageRenderQueueImpl.java:127) at $PageRenderQueue_12d2d8ecf2c.render($PageRenderQueue_12d2d8ecf2c.java) at $PageRenderQueue_12d2d8ecf24.render($PageRenderQueue_12d2d8ecf24.java) at org.apache.tapestry5.internal.services.MarkupRendererTerminator.renderMarkup(MarkupRendererTerminator.java:37) at org.apache.tapestry5.beanvalidator.BeanValidatorModule$2.renderMarkup(BeanValidatorModule.java:133) at $MarkupRenderer_12d2d8ecf2e.renderMarkup($MarkupRenderer_12d2d8ecf2e.java) at org.apache.tapestry5.services.TapestryModule$25.renderMarkup(TapestryModule.java:2026) at $MarkupRenderer_12d2d8ecf2e.renderMarkup($MarkupRenderer_12d2d8ecf2e.java) at org.apache.tapestry5.services.TapestryModule$26.renderMarkup(TapestryModule.java:2040) at $MarkupRenderer_12d2d8ecf2e.renderMarkup($MarkupRenderer_12d2d8ecf2e.java) at org.apache.tapestry5.services.TapestryModule$29.renderMarkup(TapestryModule.java:2089) at $MarkupRenderer_12d2d8ecf2e.renderMarkup($MarkupRenderer_12d2d8ecf2e.java) at org.apache.tapestry5.services.TapestryModule$28.renderMarkup(TapestryModule.java:2073) at $MarkupRenderer_12d2d8ecf2e.renderMarkup($MarkupRenderer_12d2d8ecf2e.java) at org.apache.tapestry5.services.TapestryModule$27.renderMarkup(TapestryModule.java:2055) at $MarkupRenderer_12d2d8ecf2e.renderMarkup($MarkupRenderer_12d2d8ecf2e.java) at org.apache.tapestry5.services.TapestryModule$24.renderMarkup(TapestryModule.java:2008) at $MarkupRenderer_12d2d8ecf2e.renderMarkup($MarkupRenderer_12d2d8ecf2e.java) at org.apache.tapestry5.services.TapestryModule$23.renderMarkup(TapestryModule.java:1989) at $MarkupRenderer_12d2d8ecf2e.renderMarkup($MarkupRenderer_12d2d8ecf2e.java) at $MarkupRenderer_12d2d8ecf2b.renderMarkup($MarkupRenderer_12d2d8ecf2b.java) at org.apache.tapestry5.internal.services.PageMarkupRendererImpl.renderPageMarkup(PageMarkupRendererImpl.java:47) at $PageMarkupRenderer_12d2d8ecf29.renderPageMarkup($PageMarkupRenderer_12d2d8ecf29.java) at org.apache.tapestry5.internal.services.PageResponseRendererImpl.renderPageResponse(PageResponseRendererImpl.java:67) at $PageResponseRenderer_12d2d8ece55.renderPageResponse($PageResponseRenderer_12d2d8ece55.java) at org.apache.tapestry5.internal.services.PageRenderRequestHandlerImpl.handle(PageRenderRequestHandlerImpl.java:64) at org.apache.tapestry5.services.TapestryModule$36.handle(TapestryModule.java:2326) at $PageRenderRequestHandler_12d2d8ece57.handle($PageRenderRequestHandler_12d2d8ece57.java) at $PageRenderRequestHandler_12d2d8ece51.handle($PageRenderRequestHandler_12d2d8ece51.java) at org.apache.tapestry5.internal.services.ComponentRequestHandlerTerminator.handlePageRender(ComponentRequestHandlerTerminator.java:48) at org.apache.tapestry5.services.InitializeActivePageName.handlePageRender(InitializeActivePageName.java:47) at $ComponentRequestHandler_12d2d8ece52.handlePageRender($ComponentRequestHandler_12d2d8ece52.java) at $ComponentRequestHandler_12d2d8ece36.handlePageRender($ComponentRequestHandler_12d2d8ece36.java) at org.apache.tapestry5.internal.services.PageRenderDispatcher.dispatch(PageRenderDispatcher.java:45) at $Dispatcher_12d2d8ece38.dispatch($Dispatcher_12d2d8ece38.java) at $Dispatcher_12d2d8ece33.dispatch($Dispatcher_12d2d8ece33.java) at org.apache.tapestry5.services.TapestryModule$RequestHandlerTerminator.service(TapestryModule.java:321) at org.apache.tapestry5.internal.services.RequestErrorFilter.service(RequestErrorFilter.java:26) at $RequestHandler_12d2d8ece34.service($RequestHandler_12d2d8ece34.java) at org.apache.tapestry5.services.TapestryModule$4.service(TapestryModule.java:984) at $RequestHandler_12d2d8ece34.service($RequestHandler_12d2d8ece34.java) at org.apache.tapestry5.services.TapestryModule$3.service(TapestryModule.java:974) at $RequestHandler_12d2d8ece34.service($RequestHandler_12d2d8ece34.java) at org.apache.tapestry5.internal.services.StaticFilesFilter.service(StaticFilesFilter.java:90) at
Re: [5.2.4] Bean Validation integration - another possible bug
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
Re: [5.2.4] Bean Validation integration - another possible bug
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
