>> The usecase is for tynamo's crud functionality.
>> We want to provide generic Add/List/Edit pages inside our library.
>
> The normal, unchanged URL for your pages can still be used, so you shouldn't
> worry about them. URL rewriting is aliasing, not overriding.
Of course we could use "/tynamo/add", given that we have a
LibraryMapping("tynamo","org.ourpackage").
But this does not solve the problem.. we want this site to be
accessible under the users default webapp path.
/tynamo/add should become <PATH>/add if there is no <PATH>/add available.
/tynamo/edit should become <PATH>/edit if there is no <PATH>/edit available.
and so on.
<PATH> is configured by the developer.
This would allow the developer to configure where our crud pages
should appear inside his application. Also we provide defaults inside
our library and he is able to override them by simply drop in his
implementation at the path.
> If the default page has an /admin/crud/add URL, regardless of who is
> providing it, it will work.
The problem is that "admin/crud" should be configurable.
Do you have any idea how this can be accomplished? Even if this
functionality is not yet available, maybe you have a hint what
services need to be overriden in order to make this work?
The goal is simple:
- check if there is a page available at a specific location
- if not, make tapestry think there is a page which is in fact located
somewhere else
Piero
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
