That's a feature. You can remove the ambiguity by injecting them into a non-core folder, say "/common". You'd then reference them as <t:common.foo> or <span t:type="common/foo"/>
On Jan 14, 2008 12:33 AM, Harald Geritzer <[EMAIL PROTECTED]> wrote: > > hi all, > > i am building a webapp consisting of serveral plugins each having a set of > pages which should be > injected into the "core" of the webapp. > > e.g > > webapp context: /testapp > plugin1 : /testapp/pluginpage1 > /testapp/subdir/page1 > plugin2 : /testapp/pluginpage2 > > i found out, that those pages can be addressed in two ways: > 1) the way its intended with /testapp/subdir/page1 > 2) by appending a "core" prefix: /testapp/core/subdir/page1 > tapestry renders all links using the "core"-prefix > > is it considered a bug or a feature? > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
