Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jakarta-tapestry Wiki" for change notification.
The following page has been changed by GeoffLongman: http://wiki.apache.org/jakarta-tapestry/Tapestry5LookupDebate ------------------------------------------------------------------------------ Why does removing this rule not cause the world to end? Since the convention already is that that /WEB-INF/servlet-name/ should be the location for of the application spec in the multiple-app-per-war scenario then this rule is moot even today as the previous rule (relative to the app spec location) would be hit and matched first. If the user follows the convention then not only is the rule not needed, the fact that it is there at all is just a mechanism to cause pages/components to cross namespace boundaries. Removing the rule is is like a defensive measure, applications that don't follow the convention would break in a documentable, easily explainable way. + {{{ - ''On a side note I want to state again that this ''crossing boundaries'' situation is a ''bad thing''. Tapestry already has a mechanism for sharing pages and components...libraries. Libraries are an explicit, documented, mechanism for sharing. Namespace boundary crossing is undocumented and kinda hacky don't you think?'' + As a side note I want to state again that this crossing boundaries situation is a bad thing. Tapestry already has a mechanism for sharing pages and components...libraries. Libraries are an explicit, documented, mechanism for sharing. Namespace boundary crossing is undocumented and kinda hacky don't you think? + The current implementation of Tapestry allows boundary crossing to occur implicity, without concious decision or action on the part of a developer. We all know that the implementation of Tapestry changes significantly from release to release. That means the conditions where boundary crossing could occur implicity might change from release to release. This could affect backwards compatibility as a developer, who may unknowingly be depending on this 'feature', may have thier application break in Tapestry v.X and it would be tough to diagnose the problem. + }}} + + Back to the rules... {{{ * <li><i>type</i>.jwc in WEB-INF }}} --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
