Re: cvs commit: xml-fop/examples/embedding/java/embedding ExampleFO2PDF.java

2004-07-20 Thread Jeremias Maerki
Just nitpicking, but could we call it ExampleFO2PDF-SAXParser instead of just SAX, because the transformer solution relies on SAX, too? I don't have a problem with long names. :-) On 16.07.2004 21:14:18 Simon Pepping wrote: Perhaps it is a good idea to illustrate the transformer solution in

Re: cvs commit: xml-fop/examples/embedding/java/embedding ExampleFO2PDF.java

2004-07-20 Thread Glen Mazza
I renamed it yesterday. Glen --- Jeremias Maerki [EMAIL PROTECTED] wrote: Just nitpicking, but could we call it ExampleFO2PDF-SAXParser instead of just SAX, because the transformer solution relies on SAX, too? I don't have a problem with long names. :-) On 16.07.2004 21:14:18 Simon

Re: cvs commit: xml-fop/examples/embedding/java/embedding ExampleFO2PDF.java

2004-07-20 Thread Jeremias Maerki
Great. Sorry for the noise. On 20.07.2004 22:34:28 Glen Mazza wrote: I renamed it yesterday. Glen --- Jeremias Maerki [EMAIL PROTECTED] wrote: Just nitpicking, but could we call it ExampleFO2PDF-SAXParser instead of just SAX, because the transformer solution relies on SAX, too? I

Re: cvs commit: xml-fop/examples/embedding/java/embedding ExampleFO2PDF.java

2004-07-17 Thread Glen Mazza
Good idea...this way those who prefer the SAXParserFactory method can see how FOP would work this way. (I tried to show both cases in one example, but it just made a mess of things.) If you could take care of this for us, it would be appreciated--else I'll (probably) get to it eventually. Glen

Re: cvs commit: xml-fop/examples/embedding/java/embedding ExampleFO2PDF.java

2004-07-16 Thread Simon Pepping
Glen, I can see Jeremias' argument for a single pattern to deal with all situations, but I am pleased to see the SAX solution illustrated by an example in this simplest case of all. Perhaps it is a good idea to illustrate the transformer solution in ExampleFO2PDF, and the outlying SAX parser

Re: cvs commit: xml-fop/examples/embedding/java/embedding ExampleFO2PDF.java

2004-07-15 Thread Jeremias Maerki
Glen, I'd like this change reverted. Here's the justification: VM warm-up (3 runs) VM warm-up finished. unbuffered: 766ms unbuffered: 781ms unbuffered: 766ms unbuffered: 750ms unbuffered: 703ms unbuffered: 719ms Average (unbuffered): 747ms buffered: 609ms buffered: 594ms buffered: 562ms

Re: cvs commit: xml-fop/examples/embedding/java/embedding ExampleFO2PDF.java

2004-07-15 Thread Glen Mazza
(Resending apparently...) Excellent--thanks--will do tonight. I didn't know the reason for this method, and was unsure if it was just legacy code. I'll also put a comment of how it speeds things up. Thanks, Glen --- Jeremias Maerki [EMAIL PROTECTED] wrote: Glen, I'd like this change

Re: cvs commit: xml-fop/examples/embedding/java/embedding ExampleFO2PDF.java

2004-07-15 Thread Simon Pepping
On Wed, Jul 14, 2004 at 10:42:29PM -, [EMAIL PROTECTED] wrote: gmazza 2004/07/14 15:42:29 Modified:examples/embedding/java/embedding ExampleFO2PDF.java Log: Updated FO-PDF example to use JAXP. +// Setup JAXP using identity transformer +

Re: cvs commit: xml-fop/examples/embedding/java/embedding ExampleFO2PDF.java

2004-07-15 Thread Jeremias Maerki
Because, IMO, it allows the user to use the same pattern for virtually everything: 1. Create a TransformerFactory 2. Create a Transformer and optionally use a stylesheet 3. Specify the Source (DOM, stream, file, SAX) 4. Specify the Result (DOM, stream, file, SAX) 5. Start the

Re: cvs commit: xml-fop/examples/embedding/java/embedding ExampleFO2PDF.java

2004-07-15 Thread Glen Mazza
Thanks, Simon--I didn't think of this way of solving the problem--I just modified Jeremias' previous DOM example. However, I placed the method below temporarily in the example and committed it before returning to the Transformer version. This way, we have a working example should we ever need to

Re: cvs commit: xml-fop/examples/embedding/java/embedding ExampleFO2PDF.java

2004-07-15 Thread Glen Mazza
Sounds good. --- Jeremias Maerki [EMAIL PROTECTED] wrote: Because, IMO, it allows the user to use the same pattern for virtually everything: 1. Create a TransformerFactory 2. Create a Transformer and optionally use a stylesheet 3. Specify the Source (DOM, stream, file, SAX) 4. Specify