Re: Draft Board Report for August 2015
> On 28 Jul 2015, at 14:07, Chris Bowditch wrote: > > Hi PMC, > > I have prepared the draft board report for august, which can be found here: > https://wiki.apache.org/xmlgraphics/StatusReports/StatusReportForAugust2015 > > Please review and provide feedback during the next few days. I plan to submit > this to the board in 7 days time, i.e. on 4th August Looks OK to me as well, so no suggested changes. Thanks! KR Andreas - To unsubscribe, e-mail: general-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: general-h...@xmlgraphics.apache.org
[jira] [Commented] (XGC-98) UndeclaredThrowableException while loading images
[
https://issues.apache.org/jira/browse/XGC-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14613876#comment-14613876
]
Andreas L. Delmelle commented on XGC-98:
This will solve two related issues logged against FOP that I had on my TODO
list. Already tried my initial idea, but that did not suffice, so still had to
look further, but seems like you just saved me that trouble. :)
Thanks for investigating and offering the patch!
> UndeclaredThrowableException while loading images
> -
>
> Key: XGC-98
> URL: https://issues.apache.org/jira/browse/XGC-98
> Project: XMLGraphicsCommons
> Issue Type: Bug
>Affects Versions: 1.5, 2.0.1
>Reporter: Vlad Arkhipov
>
> UndeclaredThrowableException is thrown if an image cannot be loaded for some
> reason.
> {code}
> Caused by: java.lang.reflect.UndeclaredThrowableException
> at com.sun.proxy.$Proxy313.readUnsignedInt(Unknown Source)
> at
> org.apache.xmlgraphics.image.loader.impl.PreloaderEPS.preloadImage(PreloaderEPS.java:65)
> [xmlgraphics-commons-1.5.jar:1.5]
> at
> org.apache.xmlgraphics.image.loader.ImageManager.preloadImage(ImageManager.java:175)
> [xmlgraphics-commons-1.5.jar:1.5]
> at
> org.apache.xmlgraphics.image.loader.cache.ImageCache.needImageInfo(ImageCache.java:128)
> [xmlgraphics-commons-1.5.jar:1.5]
> at
> org.apache.xmlgraphics.image.loader.ImageManager.getImageInfo(ImageManager.java:122)
> [xmlgraphics-commons-1.5.jar:1.5]
> at
> org.apache.fop.fo.flow.ExternalGraphic.bind(ExternalGraphic.java:81)
> [fop-1.1.jar:]
> at org.apache.fop.fo.FObj.processNode(FObj.java:124) [fop-1.1.jar:]
> at
> org.apache.fop.fo.FOTreeBuilder$MainFOHandler.startElement(FOTreeBuilder.java:280)
> [fop-1.1.jar:]
> at
> org.apache.fop.fo.FOTreeBuilder.startElement(FOTreeBuilder.java:175)
> [fop-1.1.jar:]
> ...
> Caused by: java.lang.reflect.InvocationTargetException
> at sun.reflect.GeneratedMethodAccessor2609.invoke(Unknown Source)
> [:1.8.0_25]
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [rt.jar:1.8.0_25]
> at java.lang.reflect.Method.invoke(Method.java:483) [rt.jar:1.8.0_25]
> at
> org.apache.xmlgraphics.image.loader.impl.AbstractImageSessionContext$ObservingImageInputStreamInvocationHandler.invoke(AbstractImageSessionContext.java:219)
> [
> xmlgraphics-commons-1.5.jar:1.5]
> ... 254 more
> Caused by: java.io.EOFException
> at
> javax.imageio.stream.ImageInputStreamImpl.readInt(ImageInputStreamImpl.java:251)
> [rt.jar:1.8.0_25]
> at
> javax.imageio.stream.ImageInputStreamImpl.readUnsignedInt(ImageInputStreamImpl.java:266)
> [rt.jar:1.8.0_25]
> ... 258 more
> {code}
> The problem being that InvocationHandlers in the classes
> AbstractImageSessionContext and ObservableStream do not handle
> InvocationTargetException properly, and the exception is propagated up to the
> proxied interface where InvocationTargetException is not specified.
> I am not sure if you accept pull requests on Github, anyway here it is
> https://github.com/apache/xml-graphics-commons/pull/1
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: general-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: general-h...@xmlgraphics.apache.org
Re: FOP's new image package in Commons?
On Dec 17, 2007, at 10:48, Jeremias Maerki wrote: Andreas, what I was talking about was exlusively logging targeted at the developer, not the user. User feedback is a different topic, one that I want to address early next year for FOP (see [1]), but I've mentioned that before. OK, just thought I'd try to kill two birds with one stone... Cheers Andreas - Apache XML Graphics Project URL: http://xmlgraphics.apache.org/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: FOP's new image package in Commons?
On Dec 16, 2007, at 10:25, Max Berger wrote: Andreas, How about using a very basic message handling system, to which users can plug in any bridge (like JCL) or specific implementation (like log4j) of their choosing? On the Commons side, this would mean at most a handful of proprietary classes/interfaces, one to which all messages are routed. Users can subclass/implement that interface to decide what to do with them in their particular context. Commons' own default implementation would simply send the messages to System.out or System.err, thereby removing any dependency on a specific logging framework whatsoever. What you are describing is exactly commons-logging :). Not really what I had in mind, or IOW: Yes, with a big BUT... There is a difference between a Logger.warn() message, which I take to be meant for developers to help debug certain issues, and ErrorListener.warning(), which is specifically meant for the external application and the end-user. I see JCL only as an abstraction for the former, not the latter. The only addition that commons-logging has is a very sophisticated (and highly criticized) auto-detection mechanism which detects the type of logging framework currently in use and will auto-plugin is specific handler. OK, and users could still opt for this solution. Only difference is: we would not be forcing the dependency on JCL down their throat, so to speak. Andreas - Apache XML Graphics Project URL: http://xmlgraphics.apache.org/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: FOP's new image package in Commons?
On Dec 13, 2007, at 09:23, Jeremias Maerki wrote: On 13.12.2007 07:46:14 The Web Maestro wrote: As for dependencies, it doesn't surprise or disappoint me much that Apache FOP and Apache Batik would require Apache XML Graphics Commons (hence the name Commons). I guess it'd be nice if features and functionality could somehow be compartmentalized, so projects (FOP, Batik, as well as external projects) could load only what they need. Hacking the Ant build is easy. There's nothing stopping anyone from proposing a patch if this becomes important. On the logging front, isn't it possible to code the Logging dependencies such that you only load the Logging functionality if it's needed/called? Source code pre-processing. Shudder. Byte code magic. Hmm. :-/ Still, I'm glad Java doesn't have "features" like C or ObjectPascal to include/exclude code parts at compile time. If it is that big an issue, as an idea to avoid this dependency altogether (and also keeping in mind the upcoming discussion concerning FOP's processing-feedback): How about using a very basic message handling system, to which users can plug in any bridge (like JCL) or specific implementation (like log4j) of their choosing? On the Commons side, this would mean at most a handful of proprietary classes/interfaces, one to which all messages are routed. Users can subclass/implement that interface to decide what to do with them in their particular context. Commons' own default implementation would simply send the messages to System.out or System.err, thereby removing any dependency on a specific logging framework whatsoever. I guess I'm thinking in the direction of something like a hybrid of a Logger (meant for development-related info) and an ErrorListener (meant for external applications/users), with the ability/feature of being able to route log-info through one channel and processing- feedback through another. The only dependency for both FOP and Batik would be on this component in Commons. Just my 2 cents Andreas - Apache XML Graphics Project URL: http://xmlgraphics.apache.org/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Max Berger for Committer
On Oct 26, 2007, at 12:36, Vincent Hennebert wrote: (replying to Vincent's reply, since Chris' original seems to have been lost in the cyber-ether again... :() +1 and I look forward to seeing the collaboration between FOP and Jeuclid strenghtened. And another +1 from me. Cheers Andreas - Apache XML Graphics Project URL: http://xmlgraphics.apache.org/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Going for 1.4 or 1.5 as minimum Java version?
On Oct 17, 2007, at 10:16, Jeremias Maerki wrote: No reactions so far. Interesting. Anyway, based on the user poll, my opinion is to go for Java 1.4 for the moment and reevaluate Java 1.5 next summer. I mean I'd love to use generics and java.util.concurrent but I think it is just a bit too soon to drop 1.4. Any objections to that course of action? Should we have a majority decision on whether 1.4 or 1.5 should be the new minimal Java level? Not as far as I'm concerned. +1 for staying with 1.4 for the time being. Chris is right. We don't really /need/ 1.5 to implement new features. It would be more a convenience than a necessity, so has very low priority IMO. Should anyone feel compelled to use 1.5, he could always integrate it much in the same way the 1.3-1.4 gap has been dealt with (separate build targets to be able to build on both versions without too much hassle). Cheers Andreas - Apache XML Graphics Project URL: http://xmlgraphics.apache.org/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Adrian Cumiskey for Committer
On Oct 10, 2007, at 16:35, Chris Bowditch wrote: I feel the time has come to promote Adrian to committer status. ... Well done Adrian! Keep up the good work! I agree very much and had already been playing with the idea of proposing it myself, so ++1 Cheers Andreas - Apache XML Graphics Project URL: http://xmlgraphics.apache.org/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release XML Graphics Commons 1.2
On Jul 17, 2007, at 16:00, Vincent Hennebert wrote: Hi I'd like to start a vote on releasing Apache XML Graphics Commons 1.2. The candidate distribution files were created from the following tag: https://svn.apache.org/repos/asf/xmlgraphics/commons/tags/commons-1_2 FWIW, here's my +1. Cheers Andreas - Apache XML Graphics Project URL: http://xmlgraphics.apache.org/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: FOP 0.94
On Jul 9, 2007, at 15:17, Vincent Hennebert wrote: J.Pietschmann a écrit : Vincent Hennebert wrote: Anyone against a new release? No. +1 to a new release. I'd volunteer to deal with all the release process... unless someone volunteers even more! Another +1 :-) Hmmm. Sorry, reading and re-reading I fail to determine what the +1 is targeted at :-\ +1 for me being the release manager... or for taking the job? Note that I don't mind if this is the latter case ;-) Knowing Joerg, I'd presume the former... He is s happy for you. ;-) Seriously: if you need that extra pair of hands, just yell. In the meantime, I'll continue scanning the patch queue to see what goodies or bugfixes we can still cram into the release before the branch is created. :-) Later Andreas - Apache XML Graphics Project URL: http://xmlgraphics.apache.org/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: FOP 0.94
On Jul 5, 2007, at 09:39, Vincent Hennebert wrote: Anyone against a new release? Nope. I'd volunteer to deal with all the release process... unless someone volunteers even more! However, I would gladly accept any help regarding updating the documentation. OK, will see what I can do. +1 Cheers Andreas - Apache XML Graphics Project URL: http://xmlgraphics.apache.org/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Jay Bryant as new committer
On Jan 24, 2007, at 01:11, The Web Maestro wrote: I'd like to propose Jay as an XML Graphics committer (FOP working set). I believe he will be a solid addition to our work force. Votes only on general@xmlgraphics.apache.org please. +1 without hesitation. Cheers, Andreas - Apache XML Graphics Project URL: http://xmlgraphics.apache.org/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Apache XML Graphics Commons 1.1
On Dec 19, 2006, at 17:40, Vincent Hennebert wrote: I'd like to start a vote on releasing Apache XML Graphics Commons 1.1. Not sure if it counts, but FWIW: +1 from me. Cheers, Andreas - Apache XML Graphics Project URL: http://xmlgraphics.apache.org/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Preparing XML Graphics Commons 1.1
On Nov 17, 2006, at 15:55, Glen Mazza wrote: 2.) Methods setColor(), setFont(), setPaint(), setBackground(), and clip() quietly just return and rely on the previous values if the caller provides a NULL argument. It should set the value to NULL instead and let the NPE occur naturally--that provides the quickest way for the developer to realize that he or she goofed up. If setFont(NULL) just relies on the previous value of the font, as it does now, it is much harder to track the error further downstream in the code. See [2]. Agreed. I'd either let the NPE occur naturally, as Glen proposes, or at least give the user-developer an indication that the use of a null argument is dubious... I remember a similar situation in FOP's properties package, but there, FOP itself was the only possible caller as the class was not part of the public API. In FOP, I remember having opted for a solution which explicitly prevented a null from being passed in as an argument to the PropertyParser, since it looked as if nulls were never supposed to make it in there. Either nulls are acceptable as an argument --but then at least something should happen, which is clearly not the case here-- or they aren't. One only needs to ask the question: "Why would anyone explicitly call those methods with a null argument?" You either set the Color or you don't, but setting the Color to null makes very little sense... If Commons cannot contain a dependency on a logging library, then Glen's proposal is the only right way to deal with this IMO. The caller could then decide to allow this dubious use of the method and catch the NPE (*), but Commons itself should not allow it (or at least: it should not take this possibility into account). (*) Note that it would be much better programming-style to avoid the method from ever being called in that case, just like it is a sign of bad style to try-and-catch an ArrayIndexOutOfBoundsException instead of making sure beforehand that the index lies within the array's bounds. A simple check to avoid the error is far more efficient than waiting for an Exception to be thrown. Just my 2 cents... Cheers, Andreas - Apache XML Graphics Project URL: http://xmlgraphics.apache.org/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Vincent Hennebert as new committer
On Oct 11, 2006, at 10:48, Jeremias Maerki wrote: I'd like to propose Vincent as an XML Graphics committer (FOP working set). I believe he will be a good addition to our work force. Absolutely no argument from me: +1 Cheers, Andreas - Apache XML Graphics Project URL: http://xmlgraphics.apache.org/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Announcement: FOP 0.92beta released
Hi all, The FOP team is very proud to present the third release off the trunk: FOP 0.92beta. It can be downloaded at: http://xmlgraphics.apache.org/fop/download.html FOP 0.92 contains a considerable amount of improvements, bugfixes and new features in comparison with last December's 0.91 release, so you're all probably wondering: Why *still* consider it a beta release? The main reason for this is a fundamental modification in the API, which was motivated by the fact that a lot of resources could be reused for multiple rendering runs. It has, of course, all been rigorously tested, but still we'd very much appreciate any feedback, especially if one of you feels there is room for improvement, be it in the area of performance or user-friendliness. Every one of your comments will be carefully weighed and taken into consideration. Due to this change, we urge you to check out the following page before starting to work with the new release: http:// xmlgraphics.apache.org/fop/0.92/embedding.html If all proceeds as planned, the next release will --finally, after some 3 years-- lose the beta-tag, since a lot of feedback and our own experiences now tell us this piece of software is ready for production environments. OTOH, if you take a look at the release notes at http:// xmlgraphics.apache.org/fop/relnotes.html, you will still see a lot of open/known issues, so... As always, code-heads are encouraged to download the sources, and start tinkering with it. Your ideas, good or bad, will be very very welcome. If you have a lot of free time and feel like joining us, all the better! ;) See you all soon on fop-users and/or fop-dev --hopefully :) May you all enjoy this release even more than the last one! Cheers, Andreas Delmelle (for the Apache XML FOP development team) - Apache XML Graphics Project URL: http://xmlgraphics.apache.org/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANNOUNCEMENT] Apache FOP 0.91 beta released
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Dec 25, 2005, at 19:37, Andreas L Delmelle wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 (Third time's the charm ;-)) Sorry, forgot to paste the links :-( Perhaps it would have been better to wait until after the weekend (filled with food and too much drinks :-P) The Apache FOP team hereby notifies you all of the release of FOP 0.91 beta, which includes various updates and bugfixes based on user feedback to the 0.90 alpha 1 release from about a month ago. The changes made since 0.91 alpha can be found here: http://xmlgraphics.apache.org/fop/changes.html The following page contains the links to the various distributions: http://xmlgraphics.apache.org/fop/download.html To those of you still using FOP 0.20.5 we would like to repeat the request to go ahead and try out the redesigned FOP. The more feedback we get, the more likely it becomes that certain features and enhancements will find their way into the codebase. If you encounter problems when upgrading, please check the following page first: http://xmlgraphics.apache.org/fop/0.91/upgrading.html If the answer to your particular problem isn't mentioned there, the FOP Team will be at your disposal on fop-users@xmlgraphics.apache.org to help guide you to a working solution. Code-grinders are, of course, always welcome to check out the source distribution and offer any ideas for enhancement and/or improvement on [EMAIL PROTECTED] Hope you enjoy! Cheers, Andreas L. Delmelle for the Apache FOP Team -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFDrub9jN5GqSO1CqkRAuJ1AJ4xRBXw0IfVHQNPQqQ8fCzouYtprgCfUMux MIDpmHZ4horsCIy1rnkWUsw= =FDju -END PGP SIGNATURE- -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFDruhTjN5GqSO1CqkRAhZ6AKCNeTE7ztT16nkHKGOKruqhLt2rLACgo/bd t1Bvb2PqGRrig5/iMNMuqGM= =cmUT -END PGP SIGNATURE- - Apache XML Graphics Project URL: http://xmlgraphics.apache.org/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANNOUNCEMENT] Apache FOP 0.91 beta released
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 (Third time's the charm ;-)) The Apache FOP team hereby notifies you all of the release of FOP 0.91 beta, which includes various updates and bugfixes based on user feedback to the 0.90 alpha 1 release from about a month ago. The changes made since 0.91 alpha can be found here: The following page contains the links to the various distributions: To those of you still using FOP 0.20.5 we would like to repeat the request to go ahead and try out the redesigned FOP. The more feedback we get, the more likely it becomes that certain features and enhancements will find their way into the codebase. If you encounter problems when upgrading, please check the following page first: If the answer to your particular problem isn't mentioned there, the FOP Team will be at your disposal on fop-users@xmlgraphics.apache.org to help guide you to a working solution. Code-grinders are, of course, always welcome to check out the source distribution and offer any ideas for enhancement and/or improvement on [EMAIL PROTECTED] Hope you enjoy! Cheers, Andreas L. Delmelle for the Apache FOP Team -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFDrub9jN5GqSO1CqkRAuJ1AJ4xRBXw0IfVHQNPQqQ8fCzouYtprgCfUMux MIDpmHZ4horsCIy1rnkWUsw= =FDju -END PGP SIGNATURE- - Apache XML Graphics Project URL: http://xmlgraphics.apache.org/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release FOP 0.91beta
On Dec 20, 2005, at 12:10, Chris Bowditch wrote: Jeremias Maerki wrote: I'd like to call for a PMC vote to release FOP 0.91beta from this newly created branch. (Votes to [EMAIL PROTECTED], please) +1 from me, obviously. +1 from me too. ... and another +1 from me. Cheers, Andreas - Apache XML Graphics Project URL: http://xmlgraphics.apache.org/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: ApacheCon US 2005 notes
On Dec 14, 2005, at 21:22, Jeremias Maerki wrote: Hey Maestro, thank you so much for reporting for us from ApacheCon. It's so good to hear that FOP was a topic there and that some of us were there to represent the project. The best of luck finding a new playground. I hope you were already successful. I second all of this. Don't worry too much about the layoff, Clay -- although I know that's easier said than done, especially in a country like the US, that has negligible social security. On the one hand, it's always the kind and generous that are subject to these things. On the other hand, my experience has taught me -- although this is in no way 'provable'-- that people ultimately always get what they deserve. I bet there's a better position somewhere out there, waiting to be filled by you. All the best, and more... Cheers, Andreas - Apache XML Graphics Project URL: http://xmlgraphics.apache.org/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
