Dear Wiki user, You have subscribed to a wiki page or wiki category on "Tapestry Wiki" for change notification.
The following page has been changed by NickWestgate: http://wiki.apache.org/tapestry/GeoffLongmanSandbox ------------------------------------------------------------------------------ In fact it's worse than this. There could be the case where an app had two links, one in a form (not an HTML form!) that would cause Tapestry to find the correct class and one that would not. When this is possible then the stability of the application is suspect because all depends on whether the first user clicked the right link. If the first click by the first user was on the bad link, the whole app is broken until the servlet container is restarted. - Currently the [http://jakarta.apache.org/tapestry/tapestry/apidocs/org/apache/tapestry/pageload/ComponentClassProvider.html ComponentClassProvider] uses a Hivemind chain to search for the page class. Passed into this chain is an instance of [http://jakarta.apache.org/tapestry/tapestry/apidocs/org/apache/tapestry/pageload/ComponentClassProvider.html ComponentClassProviderContext] which contains: + Currently the [http://tapestry.apache.org/tapestry4/tapestry/apidocs/org/apache/tapestry/pageload/ComponentClassProvider.html ComponentClassProvider] uses a Hivemind chain to search for the page class. Passed into this chain is an instance of [http://tapestry.apache.org/tapestry4/tapestry/apidocs/org/apache/tapestry/pageload/ComponentClassProvider.html ComponentClassProviderContext] which contains: * the page name * the INamespace for the page * the page specification - One member of the chain, [http://jakarta.apache.org/tapestry/tapestry/apidocs/org/apache/tapestry/pageload/NamespaceClassSearchComponentClassProvider.html NamespaceClassSearchComponentClassProvider], gets a list of packages, say {{{com.myfoo}}}, by checking a property in the Namespace and then checks each package for a class with a fully qualified name of the package with the page name appended. If the !NamespaceClassSearchComponentClassProvider does not locate a class it falls to other members of the chain and in most cases the resulting class would be {{{org.apache.tapestry.html.BasePage}}}. + One member of the chain, [http://tapestry.apache.org/tapestry4/tapestry/apidocs/org/apache/tapestry/pageload/NamespaceClassSearchComponentClassProvider.html NamespaceClassSearchComponentClassProvider], gets a list of packages, say {{{com.myfoo}}}, by checking a property in the Namespace and then checks each package for a class with a fully qualified name of the package with the page name appended. If the !NamespaceClassSearchComponentClassProvider does not locate a class it falls to other members of the chain and in most cases the resulting class would be {{{org.apache.tapestry.html.BasePage}}}. The problem arises because the page name may be a path like{{{ pages/MyPage --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
