Details
-
Bug
-
Status: Resolved
-
Minor
-
Resolution: Abandoned
-
5.0.15
-
None
-
None
-
None
-
Windows XP SP 2, Jetty Launcher 5.1.12, Maven 2.0.9, Hibernate 3.2.2, Eclipse 3.3.2, FireFox 2.0.0.15, IE7
Description
If two parameters are specified with the same name inside a grid component (for example) in a tml file, Tapestry seems to ignore the first one and render only the second.
Can Tapestry throw an exception when there is a conflict between identically named parameter components?