fop-pdf-images was updated with pdfbox-1.8.4 jars.
if you checkout and run "ant dist" you get all the jars in an archive.
On 2/5/14, 11:51 AM, Kai Hofmann wrote:
Dear Luis Bernardo,
thanks for doing the update to pdfbox 1.8.4 in advance.
I tried to apply the patches to the pdfbox trunk - where they failed and I had
some problems with figuring out the reasons (like a missing test class - which
is simple, and other moved code).
But you are right, because 1.8.4 is a bugfix release they should work there -
so I should checkout the 1.8.4 branch instead of the trunk ;-)
Greetings from Germany
PowerStat
--
Kai Hofmann EMail: powers...@web.de
Bremen/Germany
Gesendet: Mittwoch, 05. Februar 2014 um 11:03 Uhr
Von: "Luis Bernardo" <lmpmberna...@gmail.com>
An: fop-users@xmlgraphics.apache.org
Betreff: Re: Aw: Re: Fop 1.1 / fop-pdf-images / PDFBox 1.8.3/4
PDFBox-1.8.4 was only released a few days ago and that explains why
fop-pdf-images is still using 1.8.3. I will update it today.
Meanwhile, if you want to apply the two patches that fontbox needs, they
are in the lib directory of the fop project. They were created against
PDFBox-1.8.3, and possibly they can be applied cleanly to 1.8.4.
On 2/5/14, 7:09 AM, Kai Hofmann wrote:
Hello,
my experience with the official trunk version is that PDFBox-1.8.3 has a bug
that is fixed in 1.8.4 that makes it impossible to use the fop-pdf-image trunk
at the moment - so would be nice if this could be updated. I have not
understand the pdfbox patches yet, so I was not able to apply them to pdfbox
1.8.4.
As you mention the official binaries are no longer usable for me, because the
pdfbox version included is to much outdated - and I need pdfbox too in my code.
At the moment I am thinking about using a separate class loader for the
official binaries, but in my eyes this is the badest way ...
Best way for me would be if fop-pdf-images-trunk could be updated to pdfbox
1.8.4 then I will give fop-trunk a try, but with pdfbox 1.8.3 it is only broken
software for me :(
Thanks
PowerStat
Gesendet: Dienstag, 04. Februar 2014 um 14:39 Uhr
Von: "Luis Bernardo" <lmpmberna...@gmail.com>
An: "fop-users@xmlgraphics.apache.org" <fop-users@xmlgraphics.apache.org>
Betreff: Re: Fop 1.1 / fop-pdf-images / PDFBox 1.8.3/4
If you are using FOP-1.1 then you should use fop-pdf-images that you can get
from https://dist.apache.org/repos/dist/dev/xmlgraphics/binaries/. That
includes the PDFBox jars, but they are 1.3.1 only.
If you need PDFBox-1.8.3, then you should use FOP-trunk and
fop-pdf-images-trunk. Note that FOP-trunk includes a patched fontbox-1.8.3 (and
you should use it instead of the official fontbox-1.8.3). It is expected that
FOP will use the official fontbox jar in the near future.
On Tue, Feb 4, 2014 at 1:26 PM, Kai Hofmann
<powers...@web.de[powers...@web.de]> wrote:Hello *,
I have an old Fop with an old fop-pdf-images release perfectly running since
years :)
But now I updated to FOP 1.1 release, fop-pdf-images trunk (also tested 2.0.1)
and PDFBox 1.8.3/4.
That because I use PDFBox in my code also by myself with some newer features.
So my first problem was that with PDFBox 1.8.3 I got exceptions from PDFBox -
which seems to be solved with updating today to 1.8.4 :)
The problem now is different - when running in debug more nothing more happens
after the following output:
2014-02-04 10:55:01,611 [PollScheduler] DEBUG
org.apache.fop.layoutmgr.AbstractBreaker - PLM> part: 1, start at pos 0, break
at pos 3, break class = ANY
2014-02-04 10:55:01,611 [PollScheduler] DEBUG
org.apache.fop.layoutmgr.AbstractBreaker - addAreas from 0 to 0
2014-02-04 10:55:01,614 [PollScheduler] DEBUG org.apache.fop.area.IDTracker -
signalIDProcessed()
2014-02-04 10:55:01,614 [PollScheduler] DEBUG org.apache.fop.area.IDTracker -
signalIDProcessed()
2014-02-04 10:55:01,614 [PollScheduler] DEBUG org.apache.fop.area.IDTracker -
signalIDProcessed()
2014-02-04 10:55:01,960 [PollScheduler] DEBUG
org.apache.xmlgraphics.image.loader.pipeline.PipelineFactory - Pipeline:
Loader: org.apache.fop.render.pdf.pdfbox.ImageLoaderPDF@86ad0a with penalty 0
2014-02-04 10:55:01,963 [PollScheduler] DEBUG
org.apache.xmlgraphics.image.loader.pipeline.PipelineFactory - Pipeline:
Loader: org.apache.fop.render.pdf.pdfbox.ImageLoaderPDF@1a966b9 Converters:
[org.apache.fop.render.pdf.pdfbox.ImageConverterPDF2G2D@972698,
org.apache.xmlgraphics.image.loader.impl.ImageConverterG2D2Bitmap@166d0be,
org.apache.xmlgraphics.image.loader.impl.ImageConverterBuffered2Rendered@1127906,
org.apache.xmlgraphics.image.loader.impl.ImageConverterRendered2PNG@1c79e64]
with penalty 1020
2014-02-04 10:55:01,963 [PollScheduler] DEBUG
org.apache.xmlgraphics.image.loader.pipeline.PipelineFactory - Pipeline:
Loader: org.apache.fop.render.pdf.pdfbox.ImageLoaderPDF@6fe64f Converters:
[org.apache.fop.render.pdf.pdfbox.ImageConverterPDF2G2D@972698] with penalty
1000
2014-02-04 10:55:01,963 [PollScheduler] DEBUG
org.apache.xmlgraphics.image.loader.pipeline.PipelineFactory - Pipeline:
Loader: org.apache.fop.render.pdf.pdfbox.ImageLoaderPDF@7953f0 Converters:
[org.apache.fop.render.pdf.pdfbox.ImageConverterPDF2G2D@972698,
org.apache.xmlgraphics.image.loader.impl.ImageConverterG2D2Bitmap@166d0be] with
penalty 1010
2014-02-04 10:55:01,963 [PollScheduler] DEBUG
org.apache.xmlgraphics.image.loader.pipeline.PipelineFactory - Pipeline:
Loader: org.apache.fop.render.pdf.pdfbox.ImageLoaderPDF@175dce3 Converters:
[org.apache.fop.render.pdf.pdfbox.ImageConverterPDF2G2D@972698,
org.apache.xmlgraphics.image.loader.impl.ImageConverterG2D2Bitmap@166d0be,
org.apache.xmlgraphics.image.loader.impl.ImageConverterBuffered2Rendered@1127906]
with penalty 1010
2014-02-04 10:55:01,963 [PollScheduler] DEBUG
org.apache.xmlgraphics.image.loader.pipeline.PipelineFactory - Pipeline:
Loader: org.apache.fop.render.pdf.pdfbox.ImageLoaderPDF@f8f12c Converters:
[org.apache.fop.render.pdf.pdfbox.ImageConverterPDF2G2D@972698,
org.apache.fop.image.loader.batik.ImageConverterG2D2SVG@1a19cec] with penalty
1010
2014-02-04 10:55:01,963 [PollScheduler] DEBUG
org.apache.xmlgraphics.image.loader.ImageManager - Chosen pipeline: Loader:
org.apache.fop.render.pdf.pdfbox.ImageLoaderPDF@86ad0a
Looks like no crash happens, no exception, also no cpu consumtion - really
strange.
When trying the older fop-pdf-images 2.0.1 it stops (maybe) at the same point -
but gives me a warning that a pdf 1.5 was used which might result in unexpected
results. But also nothing more happens.
I also checked out the fop-pdf-images source code to find out more, but without
much luck.
One time I got a Null pointer expection from PreloaderPDF.loadPDF(..) line 117:
pddoc.getDocument().setWarnMissingClose(false);
But can't reproduce this at the moment.
Can somebody help with this?
Greetings and thanks
PowerStat
--
Kai Hofmann EMail: powers...@web.de[powers...@web.de]
Bremen/Germany
---------------------------------------------------------------------
To unsubscribe, e-mail:
fop-users-unsubscr...@xmlgraphics.apache.org[fop-users-unsubscr...@xmlgraphics.apache.org]
For additional commands, e-mail:
fop-users-h...@xmlgraphics.apache.org[fop-users-h...@xmlgraphics.apache.org]
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org