W3C home > Mailing lists > Public > xproc-dev@w3.org > January 2012

Re: why not in p:exec ... ""If cwd is not specified, the cwd is the same as the xproc file one is running."?

From: Murray Altheim <murray11@altheim.com>
Date: Thu, 19 Jan 2012 01:02:55 +1300
Message-ID: <4F16B4EF.4080101@altheim.com>
To: xproc-dev@w3.org
On 19/01/12 00:50, David Lee wrote:
> Location and PWD are different.
> Simple case, suppose the xproc "file" was served via a URL
> http://www.mine.com/xproc.xml

Another use case just popped up today: we ran into some catalog file
difficulties with file: URLs so I whipped up a handler returning a
URLConnection for a bespoke "classpath:" protocol. So we're now
shoving the entire tree of our catalogs, DTDs, XSLTs, etc. into a
jar file and just pointing to the root catalog. Works like a charm,
is fast and reliable, but it occurs to me (as a summary) that we
*will* be relying on the JVM's ability to resolve "classpath:" URLs
within the jar file, e.g.,


So for our use of XProc and all associated entities, it looks like
they won't be in a database but neither will we be locating them
on the file system.


Murray Altheim <murray12 at altheim dot com>                       = =  ===
http://www.altheim.com/murray/                                     ===  ===
SGML Grease Monkey, Banjo Player, Wantanabe Zen Monk               = =  ===

     In the evening
     The rice leaves in the garden
     Rustle in the autumn wind
     That blows through my reed hut.
            -- Minamoto no Tsunenobu
Received on Wednesday, 18 January 2012 12:03:27 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:03:09 UTC