Re: [Xpipe-developers] questions about using 0.4

[Sean M. <sea...@pr...>]

At 16:20 29/01/2002 -0500, DuCharme, Bob (LNG) wrote:
>Hello XPipers!
>
>I downloaded xpipe0.4.zip and ran the xc0 - xc3 tests fine using Windows 98
>and Sun's Java HotSpot Client VM build 1.3.0_01.

Thanks for downloading and testing!

>  I have four questions (and
>I apologize if the answers were under my nose somewhere):
>
>1. How do we tell an XComponent to use some input other than the test input,
>e.g. a foobar.xml file sitting on the hard disk?

The mainline of ExecuteXComponent.py in 0.4 is wired to run a test case.
I have changed it to run the test case if there are no command line
parameters and expect 4 parameters otherwise:
         Param 1 : The Directory in which the XComponent has been installed
         Param 2: Input File
         Param 3 : Output File
         Param 4: Log File

This will be in the CVS later today. Here is a little script that gets around
the problem by importing the ExecuteXComponent function:

# ExecuteXComponent1.py
import sys
from ExecuteXComponent import ExecuteXComponent
ExecuteXComponent (sys.argv[1],sys.argv[2],sys.argv[3],sys.argv[4])



>2. Although the Big Aspirational Plan document says that XPipes are the
>focus of the 0.4 release, and Schemas\XPipe.dtd does show me the proper
>structure of an XPipe, I don't see anything in the 0.4 distribution about
>running a pipeline. How do I use the output from one XComponent as the input
>of the next one?

I'm working on the XPipe model right now and hope to have it all up and
running by the weekend.


>3. The FAQ mentions XComponents split, scatter, gather, triggers etc., but I
>don't see these anywhere in XPipe 0.4 distribution. Where can I see
>XComponents other than xc0 - xc3?

I have some in various stages of readiness and have some work from David
Starr to fold in. Hopefully I'll have new components in by the week end.
Scatter/Gather in particular, will, I believe, make the benefits of XPipe
pipelining clear - expecially to XSLT and DOM developers hitting scaling
problems.


>4. Tell me more about executing Code with type="Exec". For example, if it's
>an Omnimark script, where would I say that Omnimark is the executable to
>run?

I hope to have this in by the weekend - using Unix tr command as an example
of an external native app. Once this works, Omnimark, Perl etc. should
be simple.

>Two points about the README file:

Thanks for the fixes.

regards,
Sean