[
https://issues.apache.org/jira/browse/TAP5-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Kemnade updated TAP5-1667:
---------------------------------
This issue has been last updated about 1.5 years ago and has no information
about the versions that are affected. That makes it hard to determine whether
it is still relevant.
If the issue still persists with the current stable version (5.3.7) or the most
recent development preview of Tapestry (5.4-beta-6), both of which are
available from Maven Central, please update it as soon as possible, adding the
respective version(s) to the issue's "Affects Version/s".
> 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=ktrp2jq5mtirw...@mail.gmail.com%3E
> Thank you all for your efforts :)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
