As far as I am aware, whilst "context://" is currently defined,
"context:/" has no meaning.
Can I propose a *very* useful definition for "context:/", accepting that I
don't know whether this is easy to implement or not ( :-) ):
A file within the context of the webapp, relative to the root of the
sitemap
or subsitemap of the externally requested page.
Let me explain further with an example to give an idea of what I mean and
why it would be *really* useful.
Imagine that we have a number of subsitemaps containing common internal
'processing' requirements which call upon 'internal' pipelines, like this
within the subsitemap:
<map:match pattern="data/*/*.xml">
<map:generate src="data/{1}/{2}.xml" />
<map:transform src="context://standard_transform.xslt" />
<map:serialize type="xml" />
</map:match>
Here, the source data is located in the subsitemap, but the standard
transform XSLT is located in the root sitemap. If we have to put this
pipeline definition in every subsitemap that uses it, there is going to be
a lot of repetition of code and lots to maintain. But his would all be
solved if we could redefine it within the root sitemap like this:
<map:match pattern="data/*/*.xml">
<map:generate src="context:/data/{1}/{2}.xml" />
<map:transform src="context://standard_transform.xslt" />
<map:serialize type="xml" />
</map:match>
Using my proposed definition of "context:/" this would locate 'data/{1}/{2}
.xml' from within the filespace of the subsitemap that called it.
What does anyone think?
Stuart.
-------------------------------------------------------------------------
Stuart Roebuck [EMAIL PROTECTED]
Lead Developer Java, XML, MacOS X, XP, etc.
ADOLOS <http://www.adolos.com/>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
