You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-dev@xmlgraphics.apache.org by Art Welch <ar...@EASTPOINT.COM> on 2001/09/17 18:45:37 UTC
RE: DO NOT REPLY [Bug 3655] New: - Driver.reset() does not func
tion properly
Also if no other action is taken - like creating a new output stream or
something - aren't we asking for a NPE?
-----Original Message-----
From: Art Welch
Sent: Monday, September 17, 2001 12:41 PM
To: 'fop-dev@xml.apache.org'
Subject: RE: DO NOT REPLY [Bug 3655] New: - Driver.reset() does not func
tion properly
Ah... I see that this is probably why Keiron added the null'ing to
Driver.reset(). I still think that nulling the output stream is not really
appropriate - especially since the output stream is not really an internal
structure of Driver (IIRC). I think that Driver does not create the output
stream. If this is correct then it probably should not null it. Actually I
think that this is a bit gray. Certainly it should not close it. But setting
it's reference to it to null... mainly I do not like it because it is
inconvenient for me and if we wanted to support concatenation in the
renderers this could be in the way.
Again... just a thought...
Art
-----Original Message-----
From: bugzilla@apache.org [mailto:bugzilla@apache.org]
Sent: Monday, September 17, 2001 11:46 AM
To: fop-dev@xml.apache.org
Subject: DO NOT REPLY [Bug 3655] New: - Driver.reset() does not function
properly
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3655>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3655
Summary: Driver.reset() does not function properly
Product: Fop
Version: 0.17
Platform: PC
OS/Version: Windows NT/2K
Status: NEW
Severity: Normal
Priority: Other
Component: general
AssignedTo: fop-dev@xml.apache.org
ReportedBy: wim.van.leuven@ldc.be
We use FOP to generate pdf reports. A Driver is instantiated to render the
pdf,
after which the driver is reset. When the same driver is reused to render
another pdf, one document is created containing the first and the new pdf.
So
both reports are appended. So I presume the reset method does not
reinitialize
the internal datastructures properly.
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org