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 2015/01/12 09:10:52 UTC
[jira] [Closed] (TAP5-1667) Non compatible component declaration in
tml and java class not firing an exception
[ https://issues.apache.org/jira/browse/TAP5-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jochen Kemnade closed TAP5-1667.
--------------------------------
Resolution: Invalid
We assume this is no longer relevant and therefore close it.
If you still have this issue in a recent Tapestry version (such as 5.3.8 or the latest 5.4 preview release), feel free to provide the necessary information and reopen.
> Non compatible component declaration in tml and java class not firing an exception
> ----------------------------------------------------------------------------------
>
> Key: TAP5-1667
> URL: https://issues.apache.org/jira/browse/TAP5-1667
> Project: Tapestry 5
> Issue Type: Improvement
> Reporter: Muhammad Gelbana
> Priority: Minor
> Labels: @Component,, @InjectComponent,
>
> I by mistake, declared a "select" component in my .tml and declared a component in the java class as TextField using @Component annotation. This is wrong as Thiago pointed out but tapestry didn't throw an exception and just showed a text field in the html shown to the user.
> =============
> *Index.tml*
> <t:select model="literal:a,b,c" value="select" t:id="select"/>
> *Index.page*
> @Property
> private String select;
> @Component(id="select")
> private *TextField* select
> ===============
> Which is wrong. But shouldn't this fire an exception ?
> Please refer to this thread for some detailed description:
> http://mail-archives.apache.org/mod_mbox/tapestry-users/201109.mbox/%3CCAOjiMm5kJL+4p=zPt3OgoaA5e0VRVgmgg=kTRp2jq5mtiRW7xA@mail.gmail.com%3E
> Thank you all for your efforts :)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)