DO NOT REPLY [Bug 30156] - Image file opened but not closed
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=30156. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=30156 Image file opened but not closed [EMAIL PROTECTED] changed: What|Removed |Added Severity|Normal |Critical --- Additional Comments From [EMAIL PROTECTED] 2004-07-30 08:20 --- I changed this to critical because in a server application, this constantly results in OutOfMemory excpetions after some time. And the only solution is to exit the application (JVM) and restart it again. So far, we have to exit our application every morning and restart it again ... :-( I noticed this as some temporary image files used for FOP transformation can't be deleted after the processing (and freeing up all possible objects).
Re: Redesign
Andrej Czapszys wrote: Please excuse my ignorance, but what is the current status of the redesign, and how might I help out? The website explanation wasn't very clear. The website is great for the maintenance versions of FOP 0.20.x, but is a little unclear with regards to the redesign (sorry Clay - I dont have any specifics to hand) In particular, extreme memory usage and inability to auto-size tables have been bugging me. The current stable version of FOP is great, but I'd like to help improve these areas and others. Is there a current TODO and/or complete status list? Follow the below link where you will find a list of items that need doing before the redesigned code can be released. Issues such as memory and auto table layout would be nice to have, but the redesign has more serious problems that need dealing with first. http://xml.apache.org/fop/design/layout.html#status-todo Of course, this is largely just my opinion and you are welcome to work on any area you choose. And any contribution you make will be greatly received. Or can someone help me out in this regard? Also, what are the current high priority issues from your perspective? I'm kind of a Roadmap personality in that I'd like to know where contributors would like the project to be in X months. Well, I'd like to see the HIGHs on that list fixed in the redesigned layout so we can do a release of the redesigned code, and get out of the rut that FOP is stuck in! snip/ Chris
DO NOT REPLY [Bug 30156] - Image file opened but not closed
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=30156.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=30156
Image file opened but not closed
--- Additional Comments From [EMAIL PROTECTED] 2004-07-30 14:08 ---
yup, it would be great to introduce a
InputStream inputStream = null;
try {
inputStream = ...
...
} finally {
if (inputStream != null) try { inputStream.close();} catch (IOException
ioe) { /* ignore or anything else */ }
}
Re: Redesign
On Jul 30, 2004, at 7:11 AM, Chris Bowditch wrote: Chris Bowditch wrote: http://xml.apache.org/fop/design/layout.html#status-todo Clay - Ive realised that this page is out of date. I updated the layout.xml in CVS about 2 months ago. Any idea why the website hasnt been updated to reflect the changes in this file? Chris I suspect (but can't confirm) it has something to do with BUILD ERRORS in /forrest/ running on forrestbot. I have been having problems getting /forrest/ to generate a successful build for some time now. Since PUBLISH worked at one time, it is possible that some update to the sitemap.xmap file causes the problem. It's also possible that updating forrest (0.5? 0.5.1?, etc.) may have caused the problem (although I doubt it). Since the forrest team is close to a 0.6 release--and I was never successful building w/ 0.5.x anyway--I thought that I might be able to just move to 0.6 and resolve the problems, thereby 'killing' two birds with one stone. I may need to rethink that. Among the current problems I'm having getting a BUILD SUCCESSFUL, the main areas are the Compliance page[1] (fairly complex table), and the sample *.fo[2] *.svg[3] files (which contain .fo files which need to be retained as RAW ** converted to PDF). I'm still working with the [EMAIL PROTECTED] team to resolve these issues. FWIW, when forrestbot.cocoondev.org was hacked (around the time I was updating the team page), I was successful at manually checking the file in (at the suggestion of JeffT)... I haven't made any other changes to the web site since, because of all of these problems I've been having with forrest. Web Maestro Clay [1] http://xml.apache.org/fop/compliance.html [2] http://xml.apache.org/fop/examples.html [3] http://xml.apache.org/fop/dev/svg.html
Re: Redesign
Chris, On Jul 30, 2004, at 7:48 AM, Clay Leeds wrote: On Jul 30, 2004, at 7:11 AM, Chris Bowditch wrote: Chris Bowditch wrote: http://xml.apache.org/fop/design/layout.html#status-todo Clay - Ive realised that this page is out of date. I updated the layout.xml in CVS about 2 months ago. Any idea why the website hasnt been updated to reflect the changes in this file? Chris I suspect (but can't confirm) it has something to do with BUILD ERRORS in /forrest/ running on forrestbot. I have been having problems getting /forrest/ to generate a successful build for some time now. snip Just to be sure, are these amongst the changes you're looking for: Justified Text High This has been completed, thanks largely to Luca Furini. Although there is still issue 28706 that requires further analysis. Multi-column layout High Get Markers Working High Main Problem is markers can be added to wrong page. LEWP is returning first on Next page! If so, I can manually upload the changes to xml-site/targets/fop/ Web Maestro Clay
