Re: svn commit: r676161 - /xmlgraphics/fop/trunk/src/java/org/apache/fop/events/model/EventModel.java
On Jul 13, 2008, at 04:07, Peter B. West wrote: Andreas Delmelle wrote: URL and URI are both used here. But I think URL is the mandatory term here. The other thing is URI Syntax which does not refer to URI itself. Since a URL is a URI, but not all URIs are URLs, I believe your example above is slightly incorrect. Nice catch. For the moment, better to be safe than sorry. Indeed, a URI could also be something not referring to a file (or, better put: a valid input source for a transformation) Strictly speaking, according to the above definition, the systemId is allowed to be a 'mailto:' (?) :-/ Sloppy editors... ;-) I don't think so. The docs for java.net.URL include The syntax of URL is defined by RFC 2396: Uniform Resource Identifiers (URI): Generic Syntax, amended by RFC 2732: Format for Literal IPv6 Addresses in URLs. That is, the syntax for URLs is defined as part of the URI syntax. Yes, that's the point, but 'URI Syntax' is more general. All URLs are URIs, but URIs can also be opaque, like a mailto:, news:, isbn:... The point is that the API docs of javax.xml.transform.stream.StreamSource do not explicitly limit the parameter to URLs. They do indicate that the constructor is meant to create a new StreamSource off a URL, but it does not even hint at the (common-sense) requirement that the parameter String actually points to a valid, live resource that can be an input source for a transformation. No immediate problem for us, but it just seems a bit sloppy on the side of the maintainers of those docs... Andreas
Re: Building FOP Trunk with Any - BUILD FAILED
Ok, I wanted to test this at home to see if this was a machine issue. Tested on: Windows XP sp2 Java(TM) SE Runtime Environment (build 1.6.0_10-ea-b12) Java HotSpot(TM) Client VM (build 11.0-b11, mixed mode, sharing) I am still unable to build with ant. I get another set of errors. I will email Jeremias the out.txt file. I also tried the the version (src/java/org/apache/fop/events/model/EventModel.java) posted, but got a bunch of errors. I will send that report to. Bones Jeremias Maerki-2 wrote: On 12.07.2008 11:56:23 Andreas Delmelle wrote: On Jul 11, 2008, at 13:22, Jeremias Maerki wrote: Bonekrusher and I had an exchange off-list. He did a few tests for me and my recent change didn't help either. Basically, we established the following: - He's also running WinXP - He's running the same JDK as I do. The /exact/ same one (identical build)? Yes, Sun 1.6.0_04 Just asking, since I remember running across some issues/ inconsistencies in the way the java.net.URL and java.net.URI translate themselves to a String. Maybe that's what's playing here... Is the warning about the deprecated File.toURL() maybe related and a hint? If it is in fact the file URL that's the problem, I'm pretty sure the problem happens within Xalan as I'm passing in a StreamResult(File). As of Java 6, the recommended way is to use File.toURI().toURL(). According to the API docs, File.toURL() does not automatically escape characters that are illegal in URLs. It is recommended that new code convert an abstract pathname into a URL by first converting it into a URI, via the toURI method, and then converting the URI into a URL via the URI.toURL method. I guess it makes sense to change all occurences now that we're on Java 1.4. I've changed the StreamSource(File) to StreamSource(File.toURI().toURL().toExternalForm()) as a first experiment. Bonekrusher can then retry on his machine. http://svn.apache.org/viewvc?rev=676161view=rev On my machine the following: System.out.println(outputFile.toURI().toASCIIString()); System.out.println(outputFile.toURI().toString()); System.out.println(outputFile.toURI().toURL().toExternalForm()); System.out.println(outputFile.toURL().toExternalForm()); yielded the following results: [eventResourceGenerator] file:/C:/Dev/FOP/main/xml-fop-temp/build/gensrc/org/apache/fop/events/event-model.xml [eventResourceGenerator] file:/C:/Dev/FOP/main/xml-fop-temp/build/gensrc/org/apache/fop/events/event-model.xml [eventResourceGenerator] file:/C:/Dev/FOP/main/xml-fop-temp/build/gensrc/org/apache/fop/events/event-model.xml [eventResourceGenerator] file:/C:/Dev/FOP/main/xml-fop-temp/build/gensrc/org/apache/fop/events/event-model.xml Just for reference, Bonekrusher got file:\C:\fop_trunk\trunk\build\gensrc\org\apache\fop\events\event-model.xml on his machine (see his first post). Makes you wonder why the implementation of toURL() then does not simply do that already... I assume this is for reasons of backward- compatibility, so as to not break any existing code that relies on that behavior (?) Probably. Cheers Andreas Jeremias Maerki -- View this message in context: http://www.nabble.com/Building-FOP-Trunk-with-Ant---BUILD-FAILED-tp18359419p18428400.html Sent from the FOP - Dev mailing list archive at Nabble.com.
Re: Building FOP Trunk with Any - BUILD FAILED
On Jul 13, 2008, at 13:23, bonekrusher wrote: Ok, I wanted to test this at home to see if this was a machine issue. Just out of curiosity, can you try to copy the following files under % FOP%/lib : serializer-2.7.0.jar xalan-2.7.0.jar xercesImpl-2.7.1.jar xml-apis-1.3.04.jar to the lib/endorsed directory in the Java home dir (create if it does not exist). Then try to run the clean build again. It's a long shot, but maybe if the Xerces/Xalan implementations are forced to be the same ones that FOP ships with... HTH! Cheers Andreas
Re: Building FOP Trunk with Any - BUILD FAILED
bonekrusher wrote: Ok, I wanted to test this at home to see if this was a machine issue. Tested on: Windows XP sp2 Java(TM) SE Runtime Environment (build 1.6.0_10-ea-b12) Java HotSpot(TM) Client VM (build 11.0-b11, mixed mode, sharing) I am still unable to build with ant. I get another set of errors. I will email Jeremias the out.txt file. I also tried the the version (src/java/org/apache/fop/events/model/EventModel.java) posted, but got a bunch of errors. I will send that report to. Bones What does ant -version tell you? How do you find out which command is being executed in Windows? In linux, you execute which ant or type ant Can you do the equivalent on your system. Can you list the files and file sizes of lib and lib/build? -- Peter B. West http://cv.pbw.id.au/ Folio http://defoe.sourceforge.net/folio/
Re: Building FOP Trunk with Any - BUILD FAILED
On Jul 13, 2008, at 14:04, Peter B. West wrote: bonekrusher wrote: Ok, I wanted to test this at home to see if this was a machine issue. Tested on: Windows XP sp2 Java(TM) SE Runtime Environment (build 1.6.0_10-ea-b12) Java HotSpot(TM) Client VM (build 11.0-b11, mixed mode, sharing) I am still unable to build with ant. I get another set of errors. I will email Jeremias the out.txt file. I also tried the the version (src/java/org/apache/fop/events/model/EventModel.java) posted, but got a bunch of errors. I will send that report to. Bones What does ant -version tell you? How do you find out which command is being executed in Windows? In linux, you execute which ant Come to think of it, also check whether there is a JAVACMD environment variable that points to a java executable in a location other than JAVA_HOME/bin. In that case, the Java home echoed by the build script may throw one off course in determining the version of Java that is actually used. Cheers Andreas
Re: Building FOP Trunk with Any - BUILD FAILED
Ok, My java home is: C:\Program Files\Java\jdk1.6.0_04 I copied the jar files to: C:\Program Files\Java\jdk1.6.0_04\lib\endorsed [still didnt work] Ant Version: Apache Ant version 1.7.1 compiled on June 27 2008 I did not have a JAVACMD environment variable - I added it and will reboot. Check back in a few minutes. Bones Andreas Delmelle-2 wrote: On Jul 13, 2008, at 14:04, Peter B. West wrote: bonekrusher wrote: Ok, I wanted to test this at home to see if this was a machine issue. Tested on: Windows XP sp2 Java(TM) SE Runtime Environment (build 1.6.0_10-ea-b12) Java HotSpot(TM) Client VM (build 11.0-b11, mixed mode, sharing) I am still unable to build with ant. I get another set of errors. I will email Jeremias the out.txt file. I also tried the the version (src/java/org/apache/fop/events/model/EventModel.java) posted, but got a bunch of errors. I will send that report to. Bones What does ant -version tell you? How do you find out which command is being executed in Windows? In linux, you execute which ant Come to think of it, also check whether there is a JAVACMD environment variable that points to a java executable in a location other than JAVA_HOME/bin. In that case, the Java home echoed by the build script may throw one off course in determining the version of Java that is actually used. Cheers Andreas -- View this message in context: http://www.nabble.com/Building-FOP-Trunk-with-Ant---BUILD-FAILED-tp18359419p1842.html Sent from the FOP - Dev mailing list archive at Nabble.com.
Re: Building FOP Trunk with Any - BUILD FAILED
Ok I ran the build under three versions of ant: Apache Ant version 1.6.5 compiled on June 2 2005 Apache Ant version 1.7.0 compiled on December 13 2006 Apache Ant version 1.7.1 compiled on June 27 2008 All failed. To rule out ant, I downloaded FOP 0.94 src and ran a successfully build. This would leave me to believe that the problem lies in the trunk version. Bones. Peter B. West wrote: NetBeans includes an ant distro. The script should sort itself out. Just try wherever nb is\java2\ant\bin\ant.bat -version Mine reports $NB_HOME/java2/ant/bin/ant -version Apache Ant version 1.7.0 compiled on December 13 2006 If you get a 1.7.0, try running the build. bonekrusher wrote: Ok, when I added JAVACMD environment variable, I can not use ant. I set the variable to: C:\Program Files\Java\jdk1.6.0_04\bin bonekrusher wrote: Ok, My java home is: C:\Program Files\Java\jdk1.6.0_04 I copied the jar files to: C:\Program Files\Java\jdk1.6.0_04\lib\endorsed [still didnt work] Ant Version: Apache Ant version 1.7.1 compiled on June 27 2008 I did not have a JAVACMD environment variable - I added it and will reboot. Check back in a few minutes. Bones Andreas Delmelle-2 wrote: On Jul 13, 2008, at 14:04, Peter B. West wrote: bonekrusher wrote: Ok, I wanted to test this at home to see if this was a machine issue. Tested on: Windows XP sp2 Java(TM) SE Runtime Environment (build 1.6.0_10-ea-b12) Java HotSpot(TM) Client VM (build 11.0-b11, mixed mode, sharing) I am still unable to build with ant. I get another set of errors. I will email Jeremias the out.txt file. I also tried the the version (src/java/org/apache/fop/events/model/EventModel.java) posted, but got a bunch of errors. I will send that report to. Bones What does ant -version tell you? How do you find out which command is being executed in Windows? In linux, you execute which ant Come to think of it, also check whether there is a JAVACMD environment variable that points to a java executable in a location other than JAVA_HOME/bin. In that case, the Java home echoed by the build script may throw one off course in determining the version of Java that is actually used. Cheers Andreas -- Peter B. West http://cv.pbw.id.au/ Folio http://defoe.sourceforge.net/folio/ -- View this message in context: http://www.nabble.com/Building-FOP-Trunk-with-Ant---BUILD-FAILED-tp18359419p18430423.html Sent from the FOP - Dev mailing list archive at Nabble.com.
Re: Building FOP Trunk with Any - BUILD FAILED
bonekrusher wrote: Ok I ran the build under three versions of ant: Apache Ant version 1.6.5 compiled on June 2 2005 Apache Ant version 1.7.0 compiled on December 13 2006 Apache Ant version 1.7.1 compiled on June 27 2008 All failed. To rule out ant, I downloaded FOP 0.94 src and ran a successfully build. This would leave me to believe that the problem lies in the trunk version. Bones. You've found a real head-scratcher. I've just done an update on fop, and run a clean, followed by package. I don't generally run the tests. The build was OK. H Can you look at the lib differences between 0.94 and trunk? -- Peter B. West http://cv.pbw.id.au/ Folio http://defoe.sourceforge.net/folio/
Re: Building FOP Trunk with Any - BUILD FAILED
Bones, just a quick check: Is there a space in the path to your checkout (e.g. C:\Documents and Settings) If so, please try moving the checkout to a dir without spaces. (e.g. C:\temp) and see if that helps. Max Am 13.07.2008 um 18:24 schrieb Peter B. West: bonekrusher wrote: Ok I ran the build under three versions of ant: Apache Ant version 1.6.5 compiled on June 2 2005 Apache Ant version 1.7.0 compiled on December 13 2006 Apache Ant version 1.7.1 compiled on June 27 2008 All failed. To rule out ant, I downloaded FOP 0.94 src and ran a successfully build. This would leave me to believe that the problem lies in the trunk version. Bones. You've found a real head-scratcher. I've just done an update on fop, and run a clean, followed by package. I don't generally run the tests. The build was OK. H Can you look at the lib differences between 0.94 and trunk? -- Peter B. West http://cv.pbw.id.au/ Folio http://defoe.sourceforge.net/folio/ PGP.sig Description: This is a digitally signed message part
Re: Building FOP Trunk with Any - BUILD FAILED
No spaces. Both trunk and Ant are as follows: c:\ant c:\fop_trunk Max Berger wrote: Bones, just a quick check: Is there a space in the path to your checkout (e.g. C:\Documents and Settings) If so, please try moving the checkout to a dir without spaces. (e.g. C:\temp) and see if that helps. Max Am 13.07.2008 um 18:24 schrieb Peter B. West: bonekrusher wrote: Ok I ran the build under three versions of ant: Apache Ant version 1.6.5 compiled on June 2 2005 Apache Ant version 1.7.0 compiled on December 13 2006 Apache Ant version 1.7.1 compiled on June 27 2008 All failed. To rule out ant, I downloaded FOP 0.94 src and ran a successfully build. This would leave me to believe that the problem lies in the trunk version. Bones. You've found a real head-scratcher. I've just done an update on fop, and run a clean, followed by package. I don't generally run the tests. The build was OK. H Can you look at the lib differences between 0.94 and trunk? -- Peter B. West http://cv.pbw.id.au/ Folio http://defoe.sourceforge.net/folio/ -- View this message in context: http://www.nabble.com/Building-FOP-Trunk-with-Ant---BUILD-FAILED-tp18359419p18431648.html Sent from the FOP - Dev mailing list archive at Nabble.com.
Re: Building FOP Trunk with Any - BUILD FAILED
On Jul 13, 2008, at 14:44, bonekrusher wrote: Ok, when I added JAVACMD environment variable, I can not use ant. I set the variable to: C:\Program Files\Java\jdk1.6.0_04\bin If any exists, the variable should contain the /full/ path to the java executable, so: C:\Program Files\Java\jdk1.6.0_04\bin\java.exe would be more correct. Anyway, if none exists, there is also no way in which this could interfere with the build-process, so it's not necessary to create one. It's only so that Ant, if it finds a JAVACMD variable, uses that java.exe, rather than the one under %JAVA_HOME%/bin, while the build script will still display the version corresponding to the latter... Andreas
Re: Building FOP Trunk with Any - BUILD FAILED
On Jul 13, 2008, at 19:34, bonekrusher wrote: Hi Bones (or can we just call you Phil ;-)) No spaces. Both trunk and Ant are as follows: c:\ant c:\fop_trunk I've just committed a small change to EventProducerCollectorTask.java that /might/ help... (?) Can you try to update your sandbox, run a clean build and report back on whether that changed anything? Thanks Andreas
DO NOT REPLY [Bug 45390] New: PDF Extensions - Prototype
https://issues.apache.org/bugzilla/show_bug.cgi?id=45390 Summary: PDF Extensions - Prototype Product: Fop Version: 1.0dev Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: general AssignedTo: fop-dev@xmlgraphics.apache.org ReportedBy: [EMAIL PROTECTED] Created an attachment (id=22249) -- (https://issues.apache.org/bugzilla/attachment.cgi?id=22249) prototype implementation for pdf:dictionary + pdf:entry The attached patch contains a working prototype implementation for PDF extension objects, as discussed on http://wiki.apache.org/xmlgraphics-fop/ExtensionsForPdf. There's still quite some unfinished business there, but it should suffice to give interested parties a starting-point (no idea when I'll be able to spend more time on this). After applying the patch, Jiri Tyr's requirement can be met by adding: pdf:dictionary type=catalog xmlns:pdf=http://xmlgraphics.apache.org/fop/extensions/pdf; pdf:entry name=PageModeFullScreen/pdf:entry /pdf:dictionary basically anywhere in the document (I think; I've only tried specifying it as a descendant of fo:root). -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
Re: Building FOP Trunk with Any - BUILD FAILED
Sure call me Phil :) I ran the svn update on the EventProducerCollectorTask.java file. Here is the stack after running ant: BUILD FAILED java.lang.NullPointerException at net.sf.saxon.event.ReceivingContentHandler.getNameCode(ReceivingConte ntHandler.java:404) at net.sf.saxon.event.ReceivingContentHandler.startElement(ReceivingCont entHandler.java:277) at org.apache.fop.events.model.EventModel.toSAX(EventModel.java:96) at org.apache.fop.events.model.EventModel.writeXMLizable(EventModel.java :116) at org.apache.fop.events.model.EventModel.saveToXML(EventModel.java:133) at org.apache.fop.tools.EventProducerCollector.saveModelToXML(EventProdu cerCollector.java:202) at org.apache.fop.tools.EventProducerCollectorTask.execute(EventProducer CollectorTask.java:70) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.jav a:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:357) at org.apache.tools.ant.Target.performTasks(Target.java:385) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337) at org.apache.tools.ant.Project.executeTarget(Project.java:1306) at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExe cutor.java:41) at org.apache.tools.ant.Project.executeTargets(Project.java:1189) at org.apache.tools.ant.Main.runBuild(Main.java:758) at org.apache.tools.ant.Main.startAnt(Main.java:217) at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257) at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104) Andreas Delmelle-2 wrote: On Jul 13, 2008, at 19:34, bonekrusher wrote: Hi Bones (or can we just call you Phil ;-)) No spaces. Both trunk and Ant are as follows: c:\ant c:\fop_trunk I've just committed a small change to EventProducerCollectorTask.java that /might/ help... (?) Can you try to update your sandbox, run a clean build and report back on whether that changed anything? Thanks Andreas -- View this message in context: http://www.nabble.com/Building-FOP-Trunk-with-Ant---BUILD-FAILED-tp18359419p18434967.html Sent from the FOP - Dev mailing list archive at Nabble.com.
Re: Building FOP Trunk with Any - BUILD FAILED
That's the exception I worked around in http://svn.apache.org/viewvc?rev=676307view=rev It shouldn't occur anymore in the latest FOP Trunk when Saxon is active. Did you only update EventProducerCollectorTask.java? Please update all of your working copy and please make sure it's a proper SVN checkout like I mentioned in one of my latest off-list mails. What happens if you do a new checkout and run that (starting from a green field)? - svn co https://svn.apache.org/repos/asf/xmlgraphics/fop/trunk/ - ant (Just for everyone's information: Phil sent me some log files and in one there was XHTML code in a Java file that contained the string viewvc so I told him I suspect that he's not working off a proper SVN working copy.) On 14.07.2008 00:59:05 bonekrusher wrote: Sure call me Phil :) I ran the svn update on the EventProducerCollectorTask.java file. Here is the stack after running ant: BUILD FAILED java.lang.NullPointerException at net.sf.saxon.event.ReceivingContentHandler.getNameCode(ReceivingConte ntHandler.java:404) at net.sf.saxon.event.ReceivingContentHandler.startElement(ReceivingCont entHandler.java:277) at org.apache.fop.events.model.EventModel.toSAX(EventModel.java:96) at org.apache.fop.events.model.EventModel.writeXMLizable(EventModel.java :116) at org.apache.fop.events.model.EventModel.saveToXML(EventModel.java:133) at org.apache.fop.tools.EventProducerCollector.saveModelToXML(EventProdu cerCollector.java:202) at org.apache.fop.tools.EventProducerCollectorTask.execute(EventProducer CollectorTask.java:70) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.jav a:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:357) at org.apache.tools.ant.Target.performTasks(Target.java:385) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337) at org.apache.tools.ant.Project.executeTarget(Project.java:1306) at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExe cutor.java:41) at org.apache.tools.ant.Project.executeTargets(Project.java:1189) at org.apache.tools.ant.Main.runBuild(Main.java:758) at org.apache.tools.ant.Main.startAnt(Main.java:217) at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257) at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104) Andreas Delmelle-2 wrote: On Jul 13, 2008, at 19:34, bonekrusher wrote: Hi Bones (or can we just call you Phil ;-)) No spaces. Both trunk and Ant are as follows: c:\ant c:\fop_trunk I've just committed a small change to EventProducerCollectorTask.java that /might/ help... (?) Can you try to update your sandbox, run a clean build and report back on whether that changed anything? Thanks Andreas -- View this message in context: http://www.nabble.com/Building-FOP-Trunk-with-Ant---BUILD-FAILED-tp18359419p18434967.html Sent from the FOP - Dev mailing list archive at Nabble.com. Jeremias Maerki
