Re: JAXP / upgrade to xerces2
Christian Geisert wrote: I finally have Joerg's JAXP patch committed (well most part of it). I want to note again that this effectively removes Xalan1 support. It is probably a good idea to remove some cruft still left in, like the Xalan1-compat libs, the build rules associated with Xalan1, and the files in the tools directory should use JAXP directly instead via the abstraction layer in tools/xslt. Moving to the default ant task for doing XSLT probably will already take care of it. I will look at it this weekend (provided the easter eggs are easy to find :) Still needs to be done: - build process (replace fop's xslt-task with ant's style-task as already done in the main branch) - hypenation generation (Joerg mentioned some problems) One problem was that the dumped hyphenation classes are not rebuilt if there the source of the generation classes is changed. Perhaps there should be an intermediate jar file built for the generator, and the dumped classes depend on it as well as on their source XML. Regards J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
JAXP / upgrade to xerces2
Hi all, I finally have Joerg's JAXP patch committed (well most part of it). FOP should now *run* with any JAXP1.1 compliant parser/transformer. I've succesfully tested it with Saxon 6.5.1 (which includes Aelfred) and JDK1.4 (which includes Crimson/Xalan). Still needs to be done: - build process (replace fop's xslt-task with ant's style-task as already done in the main branch) - hypenation generation (Joerg mentioned some problems) I think this might be a good opportunity to upgrade FOP to xerces2 (and xalan 2.3.1). The only drawback is probably that xerces ships as two jars (xmlParserAPIs.jar and xercesImpl.jar). Any Comments? Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: JAXP / upgrade to xerces2
No objections, so a +1 from me. While we're at it I think we should take the opportunity to change the fop.jar manifest Class-Path (see earlier posts on this subject), so that none of the required JARs are expected to be in a lib/ directory. fop.jar can get built into the same directory that all the other JARs are already in; this is how it will normally get used anyhow. I already posted about this once and there were no objections. If there is again no objection I am going to go ahead and do this. Regards, AHS -Original Message- From: Christian Geisert [mailto:[EMAIL PROTECTED]] Sent: March 25, 2002 2:10 PM To: [EMAIL PROTECTED] Subject: JAXP / upgrade to xerces2 Hi all, I finally have Joerg's JAXP patch committed (well most part of it). FOP should now *run* with any JAXP1.1 compliant parser/transformer. I've succesfully tested it with Saxon 6.5.1 (which includes Aelfred) and JDK1.4 (which includes Crimson/Xalan). Still needs to be done: - build process (replace fop's xslt-task with ant's style-task as already done in the main branch) - hypenation generation (Joerg mentioned some problems) I think this might be a good opportunity to upgrade FOP to xerces2 (and xalan 2.3.1). The only drawback is probably that xerces ships as two jars (xmlParserAPIs.jar and xercesImpl.jar). Any Comments? Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
