You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Jochen Kemnade (JIRA)" <ji...@apache.org> on 2014/05/13 15:23:19 UTC

[jira] [Closed] (TAP5-1164) missing or misspelled tapestry xmlns causes "Embedded component(s) defined but not found error"

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

Jochen Kemnade closed TAP5-1164.
--------------------------------

    Resolution: Not a Problem

Another year has passed since the last comment. Therefore, we assume this issue has either been resolved in the meantime or it is no longer relevant to you.
If recent versions of Tapestry (i.e. 5.4 betas and 5.3.7) are still affected, please reopen the issue and adjust the "Affected Version/s" property.

> missing or misspelled tapestry xmlns causes "Embedded component(s) defined but not found error"
> -----------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1164
>                 URL: https://issues.apache.org/jira/browse/TAP5-1164
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.1.0.5
>            Reporter: Josh Canfield
>            Priority: Minor
>              Labels: bulk-close-candidate
>
> It would be helpful if tapestry could point out when it's possible that the xmlns is missing or misspelled. If there are components defined in the class and there are no components found in the template it seems reasonable to add a line to the error message.



--
This message was sent by Atlassian JIRA
(v6.2#6252)