You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ta...@jakarta.apache.org> on 2005/11/11 04:07:04 UTC
[jira] Commented: (TAPESTRY-724) Tapestry may, in some cases, look for a page class in the wrong package
[ http://issues.apache.org/jira/browse/TAPESTRY-724?page=comments#action_12357335 ]
Howard M. Lewis Ship commented on TAPESTRY-724:
-----------------------------------------------
Beginning to look over the wiki entry. First off, I don't think I ever intended <a jwcid="@PageLink" page="/WEB-INF/MyPage"/>
The rest of this bug is about dealing with ambiguities caused by the page name not matching the name of the specification file. This *is* why I am striving to eliminate the page spec, or (more specifically) to map as directly as possible from the page name to the page class, and find the page specification (if any) from there. This is an inversion of today, where the page name must be resolved to a page specification, but we also want to resolve it to a class name, without having to explicitly list it in the page spec.
But I'll continue looking this over.
> 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: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org