Re: Still need DOM Tree processing?

what he's doing (slurping a FO file into a DOM Tree, manipulating the tree by adding RDBMS values to it, then sending the DOM Tree off to FOP to be published) with what you mention above? Yes, exactly. Take the XML2PDF example. I'm copying the important part and only have to change two lines

Re: Still need DOM Tree processing?

--- Jeremias Maerki [EMAIL PROTECTED] wrote: But FOP is not XML Commons, and IMO external users should not be directly latching on to non-XSL portions (i.e., not fonts or hyphenation, etc., things that we are expected to share) of our code that way. That would limit our ability to

Re: Still need DOM Tree processing?

A bit late to react but I'm not 100% happy with moving the two classes into apps. I was a bit surprised at the time you introduced the DOM example because the same functionality could be provided via JAXP: Using a DOMSource and a SAXResult with an identity transformer. The examples were meant

Re: Still need DOM Tree processing?

--- Jeremias Maerki [EMAIL PROTECTED] wrote: Using a DOMSource and a SAXResult with an identity transformer. Do we already have an example for this one? I'm not sure of what you mean--are you saying that Manuel can continue doing exactly what he's doing (slurping a FO file into a DOM Tree

Re: Still need DOM Tree processing?

Thanks for the information. Working with a DOM tree saves one the step of needing to place input data into XML first. So retaining this functionality in 1.0 will keep the flexibility to users in how they can approach a report-generation task. I guess we should keep it in then. Thanks, Glen

Re: Still need DOM Tree processing?

On Mon, Jul 05, 2004 at 11:20:26AM -0700, Glen Mazza wrote: Thanks for the information. Working with a DOM tree saves one the step of needing to place input data into XML first. So retaining this functionality in 1.0 will keep the flexibility to users in how they can approach a report

Re: Still need DOM Tree processing?

From: Glen Mazza [EMAIL PROTECTED] Team, But does anyone generate FO documents via DOM Trees anymore? Yes, we do in a back office fop intensive server application. Manuel

Re: Still need DOM Tree processing?

Thanks--you're the first I've heard using it. May I ask: 1) Do you manually create the FO document from scratch similar to the first example I gave in my previous email? Or, do you preload an FO file into a DOM tree, navigate it, do minor manipulations, and then send it off to be published

Re: Still need DOM Tree processing?

Glen, A 1. We do preload an FO file into a DOM tree, navigate it, do manipulations, and then send it off to be published into PDF. A 2. At the time it seemed the easier way of doing it. Would we still be doing it again instead of using XSLT? Hmm, our input data is not in XML but comes from

testing DOM input

I created a ExampleDOM2PDF class for general testing and demonstration of FOP's DOM Document handling abilities. It's in the same examples/embedded/java/embedded directory as the other embedded examples. Going against 1.0, the code appears to work fine, so Victor's recent Document-handling

RE: testing DOM input

Glen Mazza wrote: Going against 1.0, the code appears to work fine, so Victor's recent Document-handling changes in Driver doesn't appear to have raised any problems. Thanks for checking that. Someday I'll try to mess with the embedded stuff more Victor Mote

DOM

I am a new user of FOP but i want to use Xerces and i don't know how can install it. When i use the samples from Xerces the java compiler tell me org.w3c.dom.Document doesn't exist. Thanks a lot. Antonio M. Marín FernándezSADIEL, S.A.c/ Isaac Newton s/n Edificio Sadiel - Sodean, Isla de

DO NOT REPLY [Bug 5075] New: - problems with DOM input

/show_bug.cgi?id=5075 problems with DOM input Summary: problems with DOM input Product: Fop Version: all Platform: All OS/Version: Windows NT/2K Status: NEW Severity: Major Priority: Other Component: general

DO NOT REPLY [Bug 5075] - problems with DOM input

/show_bug.cgi?id=5075 problems with DOM input --- Additional Comments From [EMAIL PROTECTED] 2001-11-26 03:12 --- Created an attachment (id=823) the xml source used when the error occured - To unsubscribe, e-mail: [EMAIL

DO NOT REPLY [Bug 5075] - problems with DOM input

/show_bug.cgi?id=5075 problems with DOM input --- Additional Comments From [EMAIL PROTECTED] 2001-11-26 03:14 --- Created an attachment (id=824) the xsl source used when the error occured - To unsubscribe, e-mail: [EMAIL

AW: Does render(dom) actually work?

?? Christian -Ursprüngliche Nachricht- Von: Suhail Rashid [mailto:[EMAIL PROTECTED]] Gesendet: Donnerstag, 20. September 2001 06:29 An: [EMAIL PROTECTED] Betreff: RE: Does render(dom) actually work? Hi Savino, Make sure there are NO nulls making their way into the text nodes of your xml

Re: Does render(dom) actually work?

] Betreff: RE: Does render(dom) actually work? Hi Savino, Make sure there are NO nulls making their way into the text nodes of your xml stream. these would not give problems if u wrote the xml to a file first suhail -Original Message- From: Savino, Matt C [mailto:[EMAIL

RE: Does render(dom) actually work?

Thanks for all your help on this. I have Fop-0.20.1-src.tar. How can I tell which cvs this is? I only ask because I have no inet access right now. I did discover that render(dom) does work if I load the dom object straight from a file instead of obtaining it as the output of an xslt transform. I

Does render(dom) actually work?

Hello everyone. By any chance can someone point me to some example code which uses render(dom)? No matter what combination of driver methods or Fop versions (.17,.19,.20.1) I use I seem to get the same error: building formatting object tree setting up fonts java.lang.NullPointerException

RE: Does render(dom) actually work?

Matt, Why don't you do it all in one pass? I have a servlet, that calls some bean to get XML document in a DOM format (actually JDOM), then registers fop driver as receiver of SAX events and runs XSLT on the JDOM tree. // 1. Generate XML tree Document xmlSummary

RE: Does render(dom) actually work?

, September 19, 2001 2:03 PM To: '[EMAIL PROTECTED]' Subject: RE: Does render(dom) actually work? Matt, Why don't you do it all in one pass? I have a servlet, that calls some bean to get XML document in a DOM format (actually JDOM), then registers fop driver as receiver of SAX events and runs

RE: Does render(dom) actually work?

To: '[EMAIL PROTECTED]' Subject: RE: Does render(dom) actually work? Yuri, thanks for your help. I tried your solution and I still get the following error: building formatting object tree building formatting object tree javax.xml.transform.TransformerException