Stephan Michels wrote:
I never used Wiki, so I don't want to break something.
It is never too early or too late to learn. Read the FAQ, play a bit in the sandbox. A history is kept, so you can't really break anything.
Which XML presentation do you prefer internally SAX/DOM?
SAX as internal *representation*? Well, we have the FOTree, which is built by SAX events, the basic mathod to feed data into the processor. There should be easy methods to input data using a DOM or a stream source, like in TrAX. That's why I copied the abstraction for the input source from TrAX.
You will have a problem if you will support both representations, IHMO.
Why? XSLT processors seem to cope reasonably well.
Following solution could work.. ContentHandler = (ContentHandler)FOProcessorFactory.createSAXFOProcessor(); DOMFOProcessor = FOProcessorFactory.createDOMFOProcessor();
For me, the problem with this approach is that a new input method requires not only a new processor class but also the extension of the factory class by new method. The TrAX approach allows extensions without changes to existing interfaces. J.Pietschmann --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
