You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2014/08/27 02:31:58 UTC
[jira] [Commented] (TAP5-2377) ComponentClassResolver should ensure
that page names, component types, mixin names uniquely identify a single
class
[ https://issues.apache.org/jira/browse/TAP5-2377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14111638#comment-14111638 ]
ASF subversion and git services commented on TAP5-2377:
-------------------------------------------------------
Commit 532cfae8540ec7d77d0ebdcc46d984788d4488cd in tapestry-5's branch refs/heads/master from [~hlship]
[ https://git-wip-us.apache.org/repos/asf?p=tapestry-5.git;h=532cfae ]
TAP5-2377: ComponentClassResolver should ensure that page names, component types, mixin names uniquely identify a single class
> ComponentClassResolver should ensure that page names, component types, mixin names uniquely identify a single class
> -------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-2377
> URL: https://issues.apache.org/jira/browse/TAP5-2377
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.4
> Reporter: Howard M. Lewis Ship
>
> With all the special rules in play, package name stripping, etc., it can get a bit too confusing; extra validation is desired that identifies any situation where one logical name can map to more than one class.
--
This message was sent by Atlassian JIRA
(v6.2#6252)