You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by carlos f <ca...@yahoo.com> on 2007/09/14 18:01:27 UTC

@InjectPage in library -- Page 'XXX' not found in application namespace.

For a variety of reasons I am attempting to convert a large portion of a free
standing tapestry web application into a library.

A page in my library contains an @InjectPage annotation.  This annotation
use the name of a page specified in the library.  I double checked the
library specification file and the page entry exists and seems to be
correct.

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.

Before I spend the better part of my afternoon tracking this down . . . is
my assumption incorrect?  Is there something about libraries that won't
allow me to do this?

Carlos
-- 
View this message in context: http://www.nabble.com/%40InjectPage-in-library----Page-%27XXX%27-not-found-in-application-namespace.-tf4443595.html#a12678543
Sent from the Tapestry - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org


Re: @InjectPage in library -- Page 'XXX' not found in application namespace.

Posted by andyhot <an...@di.uoa.gr>.
- Add a JIRA for namespace in ExternalLink
AFAICT, it is missing - i can add it soon enough.

- Add another one for enhancing the InjectPage annotation to accept a 
boolean
parameter, something like useCurrentNamespace - this too can be done 
pretty quickly

- InjectPageLink and InjectExternallLink of 
http://tacos.sourceforge.net/tacos4.1/tacos-annotations/index.html
could also be enhanced




carlos f wrote:
> Renat Zubairov wrote:
>   
>> 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, thanks for the reply.
>
> Unfortunately I thought namespace handling would be a bit more seamless.  We
> are repacking large portions of free standing web applications into tapestry
> libraries.  As such there are a number of preexisting external/page links
> and page injection.  I had been hoping that these components would recognize
> their "origin namespace" and default page look ups to that namespace.  They
> don't seem to do that - in fact the external link doesn't even seem to
> support an INamespace property.
>
> I don't want to hardcode an assumed library prefix in my library.  This
> isn't a huge deal - e.g. creating a little PageLink component wrapper is
> pretty straight forward - just a little annoying.
>
> Carlos 
>
>
>
>
>   

-- 
Andreas Andreou - andyhot@apache.org - http://andyhot.di.uoa.gr
Tapestry / Tacos developer
Open Source / JEE Consulting


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org


Re: @InjectPage in library -- Page 'XXX' not found in application namespace.

Posted by carlos f <ca...@yahoo.com>.

Renat Zubairov wrote:
> 
> 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, thanks for the reply.

Unfortunately I thought namespace handling would be a bit more seamless.  We
are repacking large portions of free standing web applications into tapestry
libraries.  As such there are a number of preexisting external/page links
and page injection.  I had been hoping that these components would recognize
their "origin namespace" and default page look ups to that namespace.  They
don't seem to do that - in fact the external link doesn't even seem to
support an INamespace property.

I don't want to hardcode an assumed library prefix in my library.  This
isn't a huge deal - e.g. creating a little PageLink component wrapper is
pretty straight forward - just a little annoying.

Carlos 




-- 
View this message in context: http://www.nabble.com/%40InjectPage-in-library----Page-%27XXX%27-not-found-in-application-namespace.-tf4443595.html#a12758047
Sent from the Tapestry - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org


Re: @InjectPage in library -- Page 'XXX' not found in application namespace.

Posted by Renat Zubairov <re...@gmail.com>.
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 <ca...@yahoo.com> 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: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>


-- 
Best regards,
Renat Zubairov

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org


Re: @InjectPage in library -- Page 'XXX' not found in application namespace.

Posted by carlos f <ca...@yahoo.com>.

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: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org