Project

Profile

Help

Patch #1405

closed

apply a pipeline of XSLT transforms to source(s)

Added by Anonymous almost 21 years ago. Updated almost 9 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Internals
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Legacy ID:
sf-849409
Applies to branch:
Fix Committed on Branch:
Fixed in Maintenance Release:
Platforms:

Description

SourceForge user: gschadow

An alternative command line tool that makes it easier to

apply a pipeline of XSLT transforms to one or more

sources. Would be nice if the saxon command line tool

would do something like this, but then this is simple

enough to just use. I post it here for consideration to

add to the distribution and for others to just download

from here.

-Gunther


Files

TRAXPipe.java (9.56 KB) TRAXPipe.java Anonymous, 2003-11-26 03:48
TRAXPipe.java (9.56 KB) TRAXPipe.java Anonymous, 2003-11-26 05:45
TRAXPipe.java (9.56 KB) TRAXPipe.java Anonymous, 2003-11-26 05:46
traxpipe.zip (9.56 KB) traxpipe.zip Anonymous, 2004-05-16 04:51
Actions #1

Updated by Anonymous almost 21 years ago

SourceForge user: gschadow

Logged In: YES

user_id=575520

Fixed bug where the final transform in the chain was always a

null-transform. Hence output properties where being ignored.

Actions #2

Updated by Anonymous over 20 years ago

SourceForge user: gschadow

Logged In: YES

user_id=575520

Hi, I added more to the TRAXPipe idea. Thanks to Michael

breaking the gordian knot, this now allows you to send a big

document into a pipeline, split it at the second level element

and transform each sub-document separately, then join them

again at the end into one big document.

In the future I will handle directories as such a document set

and I will add a class to write multiple documents to an

output directory (instead of joining them together.)

enjoy,

-Gunther

Actions #3

Updated by Anonymous over 20 years ago

SourceForge user: mhkay

Logged In: YES

user_id=251681

I've been tempted a number of times to add this kind of

functionality to the Saxon command line, but I've resisted.

Turning the command line into a pipeline programming

language is not the right way to go. There is lots of scope

for tools like this, but architecturally I think they belong

in a layer above Saxon, not in Saxon itself.

Michael Kay

Actions #4

Updated by Michael Kay almost 9 years ago

  • Status changed from New to Closed

Closing this very old entry as I don't think the idea is still active, i.e. I don't think anyone is using this or is likely to develop it.

Please register to edit this issue

Also available in: Atom PDF