You are looking for request.getServletPath(), thus {request:servletPath}
not really. since servletPath for me returns the whole request, that comes in, not the pipeline, that processes the request.
for instance a sitemap declares the pipeline listed below, the sitemap is mounted to c/** on a parent-sitemap that consumes /a/b/**, where /a is the context path and b is the path of the parent sitemap.
<map:pipeline>
<map:match pattern="x/y.html">
...
</map:match>
</map:pipeline>
so what I would like is to get the external path of this pipeline above, (/a/b/c) not the whole SCRIPT_NAME (/a/b/c/x/y.html) information.
so using {request:servletPath} does not work for me here.
Well, all the methods of o.a.c.environment.Request are available through JXPath here. getContextPath() and getSitemapURI() carry some of the information you are looking for.
well the reason for wanting to do this, is that if you depend on hard coded path's for instance for redirect, you loose much of the subsitemap behaviour, where you specify the path the sitemap proceses in the parent sitemap ...
You can substract the sitemapURI from the servletPath. Look at the JXPath docs on how to apply JAVA methods here.
Look at the 2.1 samples or 2.0.5 samples. At some places the absolute path is calculated for references (in XSLT, though). Look out especially for the simple-samples2html.xsl
modules, but perhaps you can point me to another direction.
Don't forget the javadocs!
Chris.
--
C h r i s t i a n H a u l
[EMAIL PROTECTED]
fingerprint: 99B0 1D9D 7919 644A 4837 7D73 FEF9 6856 335A 9E08
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
