Hello. I thought that Xalan would transform a document (SAX) directly - on the fly - to an output document (SAX). If so, one SAX event could be directly transformed to an output SAX element - continuously.
I tested that with samples/sax2sax/SAX2SAX.java
I'va written my own content handler which behaves like a proxy except that
calling the startElement method affects a System.out.println. Second, I
redirected the output to System.out.
Running the example I got:
E:\Programme\java\xalan-j_2_2_D11\samples\SAX2SAX>java SAX2SAX
IN: Class
IN: Order
IN: Family
IN: Species
...
IN: Species
IN: Species
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<BirdInfo>
Order is: TINAMIFORMES
Family is: TINAMIDAE
Great Tinamou. Tinamus major
Highland Tinamou. Nothocercus
Little Tinamou. Crypturellus soui
Thicket Tinamou. Crypturellus cinnamomeus
...
As you can see the whole source document is loaded before one output event
is fired (I think that couldn't be a problem of the serializer, could it?).
Doesn't Xalan support direct processing?
JOERN_HEID
SAX2SAX.java
Description: Binary data
