W3C home > Mailing lists > Public > xproc-dev@w3.org > July 2009

Re: Calabash: Java API

From: David A. Lee <dlee@calldei.com>
Date: Thu, 23 Jul 2009 09:04:53 -0400
Message-ID: <4A685FF5.4040901@calldei.com>
To: Florent Georges <fgeorges@gmail.com>
CC: Toman_Vojtech@emc.com, xproc-dev@w3.org
I think its me thats confused.  

Your right I was referring to the test driver, but itself it calls into 
the xproc core so its fundamentally the same issue.
(but I was talking about calabash source, not sure which codebase your 
referring to).

Looking at your example I only see the difference being :


String path = "some/path/to/pipeline.xproc";
input.addInput("source", new Source(path));

vs

input.addInput("source", new Source("pipeline.xproc"));


The later works but not the former ?
where is "pipeline.xproc" located?


David A. Lee
dlee@calldei.com  
http://www.calldei.com
http://www.xmlsh.org
812-482-5224



Florent Georges wrote:
> 2009/7/23 David A. Lee wrote:
>
>   Hi David,
>
>   
>> [...]
>>     
>
>   
>> Then inside that test is a reference to "testpipe.xml" (the
>> xproc source).
>>     
>
>   
>> [...]
>>     
>
>   
>> Different threads in xmlsh have their own "current directory"
>> but java doesnt support per-thread pwd's, so if calabash had
>> resolved all relative URI's to the process-global PWD it would
>> break given any relative paths.
>>     
>
>   
>> So I think this is the correct way to go both from an XML
>> perspective and from a Java perspective.
>>     
>
>   Well, in your example with the test suite, I think this is a
> feature *of the test suite format* itself: how should embedded
> URIs be resolved.
>
>   About the PWD, my point is not about using the PWD, whatever is
> is defined to be, but instead to use the same resolving mechanism
> for different Source objects using a system ID, independently of
> what they are use for (as pipeline document source or input
> document source.)
>
>   To take a concrete example, the following tries to apply an
> XProc document to itself, but won't work:
>
>     String        path  = "some/path/to/pipeline.xproc";
>     Source        src   = new Source(path);
>     Pipeline      pipe  = engine.newPipeline(src);
>     PipelineInput input = new PipelineInput();
>     input.addInput("source", new Source(path));
>
>   Something like "some/path/to/some/path/to/pipeline.xproc cannot
> be found" will be the error message.  But the following will
> succeed (a little bit surprisingly IMHO):
>
>     Source        src   = new Source("some/path/to/pipeline.xproc");
>     Pipeline      pipe  = engine.newPipeline(src);
>     PipelineInput input = new PipelineInput();
>     input.addInput("source", new Source("pipeline.xproc"));
>
>   But maybe I missed your point?
>
>   Regards,
>
>   
Received on Thursday, 23 July 2009 13:05:39 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 23 July 2009 13:05:39 GMT