Any thoughts on the best way to avoid the URL prefixing by
RelativePathPrefixHandler?

I'm trying to use Wicket to serve some basic WML pages, one feature of
which is that there might be a href value of "!id!..." being used,
where the "!id!" should be treated as an absolute URL prefix.  The
issue I have is that I don't want it processed to 'href="../../!id!"'
which it is at the moment.

A pre-request/page solution would be the ideal, as I'm also serving
HTML pages from the same app, but could easily split the app into two
if that's simpler that way...

/Gwyn

Reply via email to