- 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 - [EMAIL PROTECTED] - http://andyhot.di.uoa.gr
Tapestry / Tacos developer
Open Source / JEE Consulting


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to