[ http://issues.apache.org/jira/browse/TAPESTRY-724?page=comments#action_12359356 ]
Henri Dupre commented on TAPESTRY-724: -------------------------------------- > >I see the page name as the real identity, and the fact that different pages > >can share the same page > >specification to be an unfortunate ambiguity. > > Let me turn that around. If page specs can be associated with more than one > class (whatever the name of the class is based on) there is possibly no to > build a tool like Spindle that can reasonable handle it and still be user > friendly. I don't understand this case. Why and how would a spec be able to be associated with more than one class? I can understand mapping one spec to several page names but not mapping one spec to several classes. If I understand the issue the problem to solve is deal with: <page name="P1" specification-path="pages/Page"/> <page name="P2" specification-path="pages/Page"/> Why don't thow an error message in this case if there is no .page available? I thought the .page specs were still fully supported.. so with a .page file, tapestry should be able to map from a page to a class without issues., right? And allowing .page descriptions without a class doesn't make sense to me... Either you develop specless or not. > Tapestry may, in some cases, look for a page class in the wrong package > ----------------------------------------------------------------------- > > Key: TAPESTRY-724 > URL: http://issues.apache.org/jira/browse/TAPESTRY-724 > Project: Tapestry > Type: Bug > Components: Framework > Versions: 4.0 > Reporter: Geoff Longman > Assignee: Howard M. Lewis Ship > Priority: Critical > Attachments: test.zip > > I've been trying to come up with a patch but work has been getting crazy and > I have been ill for days now. > A detailed description of the problem (and apossible solution) is to be found > here: > http://wiki.apache.org/jakarta-tapestry/GeoffLongmanSandbox > In a nutshell, if a user references a Tapestry page whose class must be found > from a given list of packages it may be the case that way they have > referenced (by name) may mislead the ComponentClassProvider to look in the > wrong package. If that happens, the class is not found and (in most cases) > BasePage is assigned as the page class. Often this will break the application > if the page depends on a class other than BasePage. Depending on how the app > is set up there could be 3 or more legal ways to reference a page by name > (path parts) but only one way will result in the right page class being > located. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
