[
https://issues.apache.org/jira/browse/TAP5-1600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13084414#comment-13084414
]
Howard M. Lewis Ship commented on TAP5-1600:
--------------------------------------------
I think I'm starting to find the issue.
It looks like Tapestry is not finding the page's component template. It first
looks on the class path and appears to decide to use placeholder
ComponentTemplate (which is empty) rather than continue on to search for the
template stored in the web application context. This could be due to a
difference in how Jetty 7 and Tomcat 5.5 resport classpath resources that is
different than the Jetty 7 used by Tapestry's test suite.
> A component that is defined inside a <t:block> does not appear as an embedded
> component, causing page-load exceptions on the event handlers for the
> embedded component
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1600
> URL: https://issues.apache.org/jira/browse/TAP5-1600
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.3
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
>
> Reported from ProQuest, but not yet verified.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
