You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2008/10/16 19:31:44 UTC
[jira] Updated: (TAP5-129) Tapestry does not always diagnose
conflicts between @Component and elements in the template correctly
[ https://issues.apache.org/jira/browse/TAP5-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAP5-129:
--------------------------------------
Summary: Tapestry does not always diagnose conflicts between @Component and elements in the template correctly (was: PageLoaderProcessor check template is invlidate.)
> Tapestry does not always diagnose conflicts between @Component and elements in the template correctly
> -----------------------------------------------------------------------------------------------------
>
> Key: TAP5-129
> URL: https://issues.apache.org/jira/browse/TAP5-129
> Project: Tapestry 5
> Issue Type: Bug
> Environment: T5.0.5
> Reporter: Jun Tsai
> Priority: Minor
>
> java:
>
> @Component(parameters={"source=posts","value=post"})
> private Loop postsLoop;
> html:
> <t:postsLoop>
> ... ...
> </postsLoop>
> log in console:
> 11:29:33.944 ERROR! [SocketListener0-0] org.apache.tapestry.internal.services.PageLoaderProcessor.loadTemplateForComponent(PageLoaderProcessor.java:456) >44> Embedded component(s) postsLoop are defined within component class lichen.pages.topic.ViewTopic, but are not present in the component template.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org