tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Donny Nadolny (JIRA)" <j...@apache.org>
Subject [jira] Created: (TAP5-1259) When the type of a component in the page class and tml don't match, the tml type is silently ignored
Date Fri, 27 Aug 2010 00:25:53 GMT
When the type of a component in the page class and tml don't match, the tml type is silently
ignored
----------------------------------------------------------------------------------------------------

                 Key: TAP5-1259
                 URL: https://issues.apache.org/jira/browse/TAP5-1259
             Project: Tapestry 5
          Issue Type: Improvement
          Components: tapestry-core
    Affects Versions: 5.1.0.5, 5.2.1, 5.2
            Reporter: Donny Nadolny
            Priority: Minor


When you have a component in the tml with any type, for example:
<input t:type="PasswordField" t:id="password"/>

And you have the component type specified differently in the page class, for example:
	@Component(id = "password")
	private TextField passwordField;

Tapestry will silently ignore the type specified in the tml. In this case, it will create
a normal text field, even though it is a password field in the tml.

I think this should be an error if the tml and java have a component with the same id but
a different type, or at least generate a warning (maybe with a page verification step when
production mode is false), rather than ignoring the type in the tml.

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


Mime
View raw message