Quoting John Gunnarsson <[EMAIL PROTECTED]>: > 1. Does any of you see any major design flaw with the model i've > described above?
That depends on the content of the application. I know of a (closed source) project that serializes JAVA objects using java.beans.XMLEncoder These XMLs are read with JDOM and the Output goes to iText. I was surprised to see this solution, but it works. As always: there is more than one way to do it. > 2. I can't find any reference that contains all the available tags in > the iText xml, where can i find this? There isn't any. > 3. I read that the XML->PDF development has discontinued for a couple of > years, despite this fact, is it safe to base a solution on this > technology? Is there anyone out there that has deployed a solution base > on iText XML->PDF, comments appreciated! I haven't used it, but the developer of UJAC has writen new XML->PDF functionality: http://ujac.sourceforge.net/ > 4. The standard XML-FO is under development, but hasn't reached a > stable version yet, so i guess it would not be wise to deploy a solution > based on that techonolgy, or .....? The FOP has been around as long as iText and it is used in lots of important projects. I wouldn't discard XML-FO as an option in favor of iText because XML-FO 'isn't stable'. In some projects it's better to use iText, in other projects XML-FO is the way to go. br, Bruno ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ iText-questions mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/itext-questions
