[ http://issues.apache.org/jira/browse/TAPESTRY-724?page=comments#action_12356408 ]
Geoff Longman commented on TAPESTRY-724: ---------------------------------------- I'm not sure that banning /WEB-INF is the way to go. Consistency is what is being sacrificed right now. Everyone's time is precious and pressures come from all sides. There is pressure on you Howard to take T4 to RC and I'm under pressure from another, albeit related, community to produce Spindle for T4. Now is a good time to address this issue since as of today I'm under orders from the boss (my wife) not work any more late nights until I kick this flu (which is now well into it's second week) anyways. You are right Howard, this is not a simple fix. I want to contribute what I find but the silence has been deafening. Sometimes you have to raise your voice when it appears to fall on deaf ears. > 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]
