Umm...never mind, my original ideas are not proving to
be the best on *both* of my proposed votes this
week...quite humbling.
1) As for short-circuiting an XML stream into an XSLFO
InputStream within the CommandLineOptions, Jeremias
had pointed out that the buffering would be a
performance/memory
Team,
We're currently creating equivalent XMLReaders for the
FO Tree in two places, the Driver class (within the
run() method) and within the InputHandler class
get/createParser() methods (with an additional
SetParserFeatures() within the Starter class).
I'd like to centralize all this into
Yes, I said InputHandler is where the parser is
created--I just want that moved over to Driver
(because driver is creating them to, with its own
local instance, for external servlet usage). This
will help Victor's API simplification, also might help
us deprecate InputHandler a bit.
When TRAX and
I'll look into it. Actually, I got my complaint
wrong--I have less problem with something in apps
referencing the rest of the app (something it's doing
1,000 times already) than the *other* direction.)
Glen
--- Jeremias Maerki [EMAIL PROTECTED] wrote:
I don't see a problem with the apps
