Hi,
we would like to embed JackRabbit and offer user specific views.
For example, when a user requests
*/content/repo/documents/mydoc.txt*
a filter identifies some user specific id and forwards internally to
*/content/repository/${id}/documents/mydoc.txt*
(assume /content is the context path of the web application).
When doing so, the WebDAV response generated by JackRabbit nevertheless
contain <DAV:href> tags referring to the second URL rather to the first.
*Question: *
Is there a way to tell JackRabbit to actually assume a different "base
URL" when, for example, listing resources?
Thanks!
Henning
|