You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2014/08/27 02:07:57 UTC

[jira] [Created] (TAP5-2377) ComponentClassResolver should ensure that page names, component types, mixin names uniquely identify a single class

Howard M. Lewis Ship created TAP5-2377:
------------------------------------------

             Summary: 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)