Hello Carlos, Your assumptions are completely correct, you can address anything you want from the library (e.g. pages) inside the library namespace via namespace:BlahBlah format.
Renat On 14/09/2007, carlos f <[EMAIL PROTECTED]> wrote: > > > carlos f wrote: > > > > I am working under the assumption that page/component resolution is > > "scoped" inside of a library. So that unqualified references (e.g. > > "ComponentName" versus "myLibrary:ComponentName") are treated as local to > > the library. > > > > BTW - I am using tap 4.1.2. > > It looks like my assumption is incorrect: > > http://www.nabble.com/Default-namespace-in-a-library---tf3064457.html#a8522702 > > Is the "default library namespace" scope only valid in a few spots such as > PageLink and <component/> entries in page/component specification? > > Do I have to explicitly manage the namespace whenever: > > - injecting a page, > - locating a page with the RequestCycle, or > - returning a string from a listener method? > > Carlos > -- > View this message in context: > http://www.nabble.com/%40InjectPage-in-library----Page-%27XXX%27-not-found-in-application-namespace.-tf4443595.html#a12679026 > Sent from the Tapestry - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Best regards, Renat Zubairov --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
