You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Robert Zeigler (JIRA)" <ji...@apache.org> on 2009/07/16 21:40:15 UTC

[jira] Assigned: (TAP5-784) Exception message when componentClassName is unknown should be clearer

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

Robert Zeigler reassigned TAP5-784:
-----------------------------------

    Assignee: Robert Zeigler

> Exception message when componentClassName is unknown should be clearer
> ----------------------------------------------------------------------
>
>                 Key: TAP5-784
>                 URL: https://issues.apache.org/jira/browse/TAP5-784
>             Project: Tapestry 5
>          Issue Type: Improvement
>    Affects Versions: 5.1.0.5
>            Reporter: Robert Zeigler
>            Assignee: Robert Zeigler
>            Priority: Minor
>
> If you do something like:
> <input t:id="myfield" .../>
> And you forget to specify the type in the template, and you don't specify the type via @Component in the containing page/component class, you get an exception:
> Failure creating embedded component 'xxx' of <pagename>: java.lang.NullPointerException
> with a stack trace pointing down somewhere in the class loader.  Basically, PageLoaderImpl.startComponent assumes that either embeddedModel is not null, or token.getType() is not null, without ever checking that assumption.
> Tapestry should check the assumption and throw an exception if it is violated.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.