You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Matheus Eduardo Machado Moreira (JIRA)" <ji...@apache.org> on 2010/12/28 19:32:45 UTC
[jira] Created: (TAP5-1393) Exception thrown when rendering Form
with validate parameter bound to a bean that is null after onActivate()
Exception thrown when rendering Form with validate parameter bound to a bean that is null after onActivate()
------------------------------------------------------------------------------------------------------------
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
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.
[jira] Closed: (TAP5-1393) Form component shoould push the
BeanValidationContext into the Environment only after onPrepare()
Posted by "Igor Drobiazko (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Drobiazko closed TAP5-1393.
--------------------------------
Resolution: Fixed
Fix Version/s: 5.3.0
Thank you for the bug report.
> 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.
[jira] Closed: (TAP5-1393) Form component shoould push the
BeanValidationContext into the Environment only after onPrepare()
Posted by "Igor Drobiazko (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Drobiazko closed TAP5-1393.
--------------------------------
Resolution: Fixed
Fix Version/s: 5.3.0
Thank you for the bug report.
> 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.
[jira] Commented: (TAP5-1393) Form component shoould push the
BeanValidationContext into the Environment only after onPrepare()
Posted by "Matheus Eduardo Machado Moreira (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977809#action_12977809 ]
Matheus Eduardo Machado Moreira commented on TAP5-1393:
-------------------------------------------------------
Igor, it was a pleasure to contribute a little bit to Tapestry. :-)
> 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.
[jira] Updated: (TAP5-1393) Form component shoould push the
BeanValidationContext into the Environment only after onPrepare()
Posted by "Igor Drobiazko (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (TAP5-1393) Form component shoould push the
BeanValidationContext into the Environment only after onPrepare()
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (TAP5-1393) Exception thrown when rendering Form
with validate parameter bound to a bean that is null after onActivate()
Posted by "Matheus Eduardo Machado Moreira (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matheus Eduardo Machado Moreira updated TAP5-1393:
--------------------------------------------------
Attachment: stacktrace.txt
> Exception thrown when rendering Form with validate parameter bound to a bean that is null after onActivate()
> ------------------------------------------------------------------------------------------------------------
>
> 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
> 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.
[jira] Updated: (TAP5-1393) Form component shoould push the
BeanValidationContext into the Environment only after onPrepare()
Posted by "Igor Drobiazko (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Assigned: (TAP5-1393) Exception thrown when rendering Form
with validate parameter bound to a bean that is null after onActivate()
Posted by "Igor Drobiazko (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Drobiazko reassigned TAP5-1393:
------------------------------------
Assignee: Igor Drobiazko
> Exception thrown when rendering Form with validate parameter bound to a bean that is null after onActivate()
> ------------------------------------------------------------------------------------------------------------
>
> 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.
[jira] Updated: (TAP5-1393) Exception thrown when rendering Form
with validate parameter bound to a bean that is null after onActivate()
Posted by "Matheus Eduardo Machado Moreira (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matheus Eduardo Machado Moreira updated TAP5-1393:
--------------------------------------------------
Attachment: EditarPermissao.tml
EditarPermissao.java
Permissao.java
> Exception thrown when rendering Form with validate parameter bound to a bean that is null after onActivate()
> ------------------------------------------------------------------------------------------------------------
>
> 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
> Attachments: EditarPermissao.java, EditarPermissao.tml, Permissao.java
>
>
> 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.
[jira] Commented: (TAP5-1393) Form component shoould push the
BeanValidationContext into the Environment only after onPrepare()
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (TAP5-1393) Exception thrown when rendering Form
with validate parameter bound to a bean that is null after onActivate()
Posted by "Matheus Eduardo Machado Moreira (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matheus Eduardo Machado Moreira updated TAP5-1393:
--------------------------------------------------
Attachment: stacktrace.txt
> Exception thrown when rendering Form with validate parameter bound to a bean that is null after onActivate()
> ------------------------------------------------------------------------------------------------------------
>
> 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
> 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.
[jira] Commented: (TAP5-1393) Form component shoould push the
BeanValidationContext into the Environment only after onPrepare()
Posted by "Matheus Eduardo Machado Moreira (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977809#action_12977809 ]
Matheus Eduardo Machado Moreira commented on TAP5-1393:
-------------------------------------------------------
Igor, it was a pleasure to contribute a little bit to Tapestry. :-)
> 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.
[jira] Updated: (TAP5-1393) Exception thrown when rendering Form
with validate parameter bound to a bean that is null after onActivate()
Posted by "Matheus Eduardo Machado Moreira (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matheus Eduardo Machado Moreira updated TAP5-1393:
--------------------------------------------------
Attachment: EditarPermissao.tml
EditarPermissao.java
Permissao.java
> Exception thrown when rendering Form with validate parameter bound to a bean that is null after onActivate()
> ------------------------------------------------------------------------------------------------------------
>
> 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
> Attachments: EditarPermissao.java, EditarPermissao.tml, Permissao.java
>
>
> 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.
[jira] Assigned: (TAP5-1393) Exception thrown when rendering Form
with validate parameter bound to a bean that is null after onActivate()
Posted by "Igor Drobiazko (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Drobiazko reassigned TAP5-1393:
------------------------------------
Assignee: Igor Drobiazko
> Exception thrown when rendering Form with validate parameter bound to a bean that is null after onActivate()
> ------------------------------------------------------------------------------------------------------------
>
> 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.