tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Igor Drobiazko (JIRA)" <j...@apache.org>
Subject [jira] Updated: (TAP5-1393) Form component shoould push the BeanValidationContext into the Environment only after onPrepare()
Date Wed, 05 Jan 2011 15:34:46 GMT

     [ https://issues.apache.org/jira/browse/TAP5-1393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Igor Drobiazko updated TAP5-1393:
---------------------------------

    Summary: Form component shoould push the BeanValidationContext into the Environment only
after onPrepare()  (was: Exception thrown when rendering Form with validate parameter bound
to a bean that is null after onActivate())

> 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
>         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.


Mime
View raw message