[
https://issues.apache.org/jira/browse/TAP5-1393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12983011#action_12983011
]
Hudson commented on TAP5-1393:
------------------------------
Integrated in tapestry-5.2-freestyle #252 (See
[https://hudson.apache.org/hudson/job/tapestry-5.2-freestyle/252/])
> Form component shoould push the BeanValidationContext into the Environment
> only after onPrepare()
> -------------------------------------------------------------------------------------------------
>
> Key: TAP5-1393
> URL: https://issues.apache.org/jira/browse/TAP5-1393
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-beanvalidator
> Affects Versions: 5.2.4
> Reporter: Matheus Eduardo Machado Moreira
> Assignee: Igor Drobiazko
> Fix For: 5.3.0
>
> Attachments: EditarPermissao.java, EditarPermissao.tml,
> Permissao.java, stacktrace.txt
>
>
> An exception is throw when trying to render a Form whose validate parameter
> is bound to a bean that is null after onActivate():
> ERROR tapestry.render.br.com.eteg.cromoup.pages.acesso.EditarPermissao -
> Render queue error in BeginRender[acesso/EditarPermissao:nome]: Class cannot
> be null
> The attached files show a scenario where the bug occur. Basically it shows an
> edit page that initialize a bean (that is bound to the validate parameter of
> the Form) at onValidate() if a not-null id is passed as the initialization
> context. If the id is null the bean is initialized at onPrepare(), just after
> the Form starts to render itself. The problem seems to happen because the
> "prepare" (and "prepare_to_render") event are triggered *after* the Form
> component pushes a BeanValidationContextImpl into the Environment.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
