[ http://issues.apache.org/jira/browse/TAPESTRY-724?page=comments#action_12356303 ]
Geoff Longman commented on TAPESTRY-724: ---------------------------------------- Obviously I have not made my case clearly enough to generate even one comment. While this issue has been in JIRA for 6 days it has been a bug in my ear for 27 days and I emailed Howard privately on the first day. This all started as I'm trying to get Spindle updated for Tapestry 4 and I encountered what I feel is a serious bug in T4. It's behaviour that I'm loath to duplicate in Spindle as it is a tool that garners all of it's data from the static representation of a Tapestry project. The changes in the SpecificationResolver/PageLoader in T4 move this class lookup out of the static information and into the runtime behaviour of Tapestry. Spindle has never and will never try to duplicate the runtime behaviour of Tapestry. But that's beside the point, Tapestry is broken and nobody seems to care. I have ideas and suggestions on how to fix this but they are obviously skewed towards making my life as the Spindle developer easier and that may clash with the vision for Tapestry as a whole. Without any discussion on the issue I'm wasting my time even looking any further. Maybe I'm a bit short tempered as I have been ill for the last week but I'm fed up. I hate it that I feel driven to make the following statement... Consider Spindle for T4 on hold indefinitey until something moves on this issue. > 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 > 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]
