You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Derek E (JIRA)" <ji...@apache.org> on 2012/06/19 22:54:42 UTC
[jira] [Created] (WICKET-4615) checkRendering message should also
mention XHTML tags as a possible cause
Derek E created WICKET-4615:
-------------------------------
Summary: checkRendering message should also mention XHTML tags as a possible cause
Key: WICKET-4615
URL: https://issues.apache.org/jira/browse/WICKET-4615
Project: Wicket
Issue Type: Improvement
Components: wicket
Affects Versions: 1.5.4
Reporter: Derek E
Priority: Minor
When working in development mode with warnings turned on, it's not uncommon to get an error message like the one below when components are added in code, but not found in markup.
"org.apache.wicket.WicketRuntimeException: The component(s) below failed to render. A common problem is that you have added a component in code but forgot to reference it in the markup (thus the component will never be rendered)."
This is useful, but doesn't go far enough when assisting new developers. Another common cause that I've seen often is a component is defined and added in a parent class (e.g. AbstractBasePanel), but the child class markup file is missing the <wicket:extend> elements.
I would like to see the messaging include a statement like: "If your components were added in a parent Page or Panel, make sure the markup for your child MarkupContainer includes the appropriate Wicket XHTML tags such as <wicket:extend>."
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (WICKET-4615) checkRendering message should also
mention XHTML tags as a possible cause
Posted by "Martin Grigorov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-4615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Grigorov resolved WICKET-4615.
-------------------------------------
Resolution: Fixed
Fix Version/s: 1.5.8
6.0.0-RC1
Assignee: Martin Grigorov
> checkRendering message should also mention XHTML tags as a possible cause
> -------------------------------------------------------------------------
>
> Key: WICKET-4615
> URL: https://issues.apache.org/jira/browse/WICKET-4615
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 1.5.4
> Reporter: Derek E
> Assignee: Martin Grigorov
> Priority: Minor
> Labels: documentation, newbie
> Fix For: 6.0.0-RC1, 1.5.8
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> When working in development mode with warnings turned on, it's not uncommon to get an error message like the one below when components are added in code, but not found in markup.
> "org.apache.wicket.WicketRuntimeException: The component(s) below failed to render. A common problem is that you have added a component in code but forgot to reference it in the markup (thus the component will never be rendered)."
> This is useful, but doesn't go far enough when assisting new developers. Another common cause that I've seen often is a component is defined and added in a parent class (e.g. AbstractBasePanel), but the child class markup file is missing the <wicket:extend> elements.
> I would like to see the messaging include a statement like: "If your components were added in a parent Page or Panel, make sure the markup for your child MarkupContainer includes the appropriate Wicket XHTML tags such as <wicket:extend>."
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira