This is how to do it.

I would like Saxon to go away instead of barf if it has no input and to be silent rather than insist on outputting something if there is nothing to say because it makes life tough for imperative pipe-oriented shell scripting.

In future xmlsh rather than bash looks a more promising starting point.

On Thu, Dec 12, 2013 at 9:18 AM, Ihe Onwuka <> wrote:
The idea is to pipe input into 2 different transforms which I am trying to accomplish by the bash tee command

<piped input> | tee calltoSaxon Transform1 | calltoSaxon Transform2

Alas I am currently gnashing my teeth against a message Text File Busy.

The option to use multiple result documents and write an OutputURIResolver is not appealing.

Any clues.