You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-users@xmlgraphics.apache.org by Kai Hofmann <po...@web.de> on 2014/02/04 14:26:03 UTC
Fop 1.1 / fop-pdf-images / PDFBox 1.8.3/4
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: powerstat@web.de
Bremen/Germany
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
Aw: Re: Fop trunk / fop-pdf-images / PDFBox 1.8.4 -additional infos
Posted by Kai Hofmann <po...@web.de>.
Dear Luis Bernardo,
I have to check if I share the Factory between threads - might be possible.
Thanks for running the single thread test.
In the meantime I have created a small test example - which should repoduce the problem - but it runs without producing the exception. So I will have a much deeper look at the problem and come back when I find out more.
Greetings
PowerStat
--
Kai Hofmann EMail: powerstat@web.de
Bremen/Germany
Gesendet: Sonntag, 09. Februar 2014 um 23:48 Uhr
Von: "Luis Bernardo" <lm...@gmail.com>
An: fop-users@xmlgraphics.apache.org
Betreff: Re: Fop trunk / fop-pdf-images / PDFBox 1.8.4 -additional infos
Are you sharing the FopFactory between threads?
I ran an intense single threaded test that reuses the FopFactory and had
no problem. If you are running single thread then send your PDF so that
we can investigate.
On 2/6/14, 1:20 PM, Kai Hofmann wrote:
> I have some additional information to the NullPointerException:
>
> - the result of pddoc.getDocument() (line 117) is Null
> - the Exception only occurs when reusing the FopFactory - never during the first run.
>
> Maybe a problem with reusing the PDFBox? I will try to have a deeper look.
>
> Greetings
>
> PowerStat
>
>
> --
> Kai Hofmann EMail: powerstat@web.de
> Bremen/Germany
>
>
>
> Gesendet: Donnerstag, 06. Februar 2014 um 13:27 Uhr
> Von: "Kai Hofmann" <po...@web.de>
> An: fop-users@xmlgraphics.apache.org
> Betreff: Re: Fop trunk / fop-pdf-images / PDFBox 1.8.4
> Dear Luis Bernadro,
>
> I have now created a complete trunk version (fop, fop-pdf-image with pdfbox 1.8.4 (patched), xmlgraphics trunk, batik trunk).
> Now I end up with the following stack trace:
>
> Caused by: java.lang.NullPointerException
> at org.apache.fop.render.pdf.pdfbox.PreloaderPDF.loadPDF(PreloaderPDF.java:117)
> at org.apache.fop.render.pdf.pdfbox.PreloaderPDF.preloadImage(PreloaderPDF.java:83)
> at org.apache.xmlgraphics.image.loader.ImageManager.preloadImage(ImageManager.java:176)
> at org.apache.xmlgraphics.image.loader.cache.ImageCache.needImageInfo(ImageCache.java:128)
> at org.apache.xmlgraphics.image.loader.ImageManager.getImageInfo(ImageManager.java:123)
> at org.apache.fop.fo.flow.ExternalGraphic.bind(ExternalGraphic.java:81)
> at org.apache.fop.fo.FObj.processNode(FObj.java:129)
> at org.apache.fop.fo.FOTreeBuilder$MainFOHandler.startElement(FOTreeBuilder.java:289)
> at org.apache.fop.fo.FOTreeBuilder.startElement(FOTreeBuilder.java:178)
> at org.apache.xalan.transformer.TransformerIdentityImpl.startElement(TransformerIdentityImpl.java:1073)
> at org.apache.xml.serializer.TreeWalker.startNode(TreeWalker.java:359)
> at org.apache.xml.serializer.TreeWalker.traverse(TreeWalker.java:145)
> at org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdentityImpl.java:390)
>
> Do you have an idear about this?
>
> Greetings
>
> PowerStat
>
> --
> Kai Hofmann EMail: powerstat@web.de
> Bremen/Germany
>
>
>
> Gesendet: Donnerstag, 06. Februar 2014 um 02:12 Uhr
> Von: "Luis Bernardo" <lm...@gmail.com>
> An: fop-users@xmlgraphics.apache.org
> Betreff: Re: Aw: Re: Re: Fop 1.1 / fop-pdf-images / PDFBox 1.8.3/4
> 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: powerstat@web.de
>> Bremen/Germany
>>
>>
>>
>> Gesendet: Mittwoch, 05. Februar 2014 um 11:03 Uhr
>> Von: "Luis Bernardo" <lm...@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" <lm...@gmail.com>
>>> An: "fop-users@xmlgraphics.apache.org" <fo...@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 <powerstat@web.de[powerstat@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: powerstat@web.de[powerstat@web.de]
>>> Bremen/Germany
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org[fop-users-unsubscribe@xmlgraphics.apache.org]
>>> For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org[fop-users-help@xmlgraphics.apache.org]
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
>>> For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
>> For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
>> For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
> For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
> For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
> For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
Re: Fop trunk / fop-pdf-images / PDFBox 1.8.4 -additional infos
Posted by Luis Bernardo <lm...@gmail.com>.
Are you sharing the FopFactory between threads?
I ran an intense single threaded test that reuses the FopFactory and had
no problem. If you are running single thread then send your PDF so that
we can investigate.
On 2/6/14, 1:20 PM, Kai Hofmann wrote:
> I have some additional information to the NullPointerException:
>
> - the result of pddoc.getDocument() (line 117) is Null
> - the Exception only occurs when reusing the FopFactory - never during the first run.
>
> Maybe a problem with reusing the PDFBox? I will try to have a deeper look.
>
> Greetings
>
> PowerStat
>
>
> --
> Kai Hofmann EMail: powerstat@web.de
> Bremen/Germany
>
>
>
> Gesendet: Donnerstag, 06. Februar 2014 um 13:27 Uhr
> Von: "Kai Hofmann" <po...@web.de>
> An: fop-users@xmlgraphics.apache.org
> Betreff: Re: Fop trunk / fop-pdf-images / PDFBox 1.8.4
> Dear Luis Bernadro,
>
> I have now created a complete trunk version (fop, fop-pdf-image with pdfbox 1.8.4 (patched), xmlgraphics trunk, batik trunk).
> Now I end up with the following stack trace:
>
> Caused by: java.lang.NullPointerException
> at org.apache.fop.render.pdf.pdfbox.PreloaderPDF.loadPDF(PreloaderPDF.java:117)
> at org.apache.fop.render.pdf.pdfbox.PreloaderPDF.preloadImage(PreloaderPDF.java:83)
> at org.apache.xmlgraphics.image.loader.ImageManager.preloadImage(ImageManager.java:176)
> at org.apache.xmlgraphics.image.loader.cache.ImageCache.needImageInfo(ImageCache.java:128)
> at org.apache.xmlgraphics.image.loader.ImageManager.getImageInfo(ImageManager.java:123)
> at org.apache.fop.fo.flow.ExternalGraphic.bind(ExternalGraphic.java:81)
> at org.apache.fop.fo.FObj.processNode(FObj.java:129)
> at org.apache.fop.fo.FOTreeBuilder$MainFOHandler.startElement(FOTreeBuilder.java:289)
> at org.apache.fop.fo.FOTreeBuilder.startElement(FOTreeBuilder.java:178)
> at org.apache.xalan.transformer.TransformerIdentityImpl.startElement(TransformerIdentityImpl.java:1073)
> at org.apache.xml.serializer.TreeWalker.startNode(TreeWalker.java:359)
> at org.apache.xml.serializer.TreeWalker.traverse(TreeWalker.java:145)
> at org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdentityImpl.java:390)
>
> Do you have an idear about this?
>
> Greetings
>
> PowerStat
>
> --
> Kai Hofmann EMail: powerstat@web.de
> Bremen/Germany
>
>
>
> Gesendet: Donnerstag, 06. Februar 2014 um 02:12 Uhr
> Von: "Luis Bernardo" <lm...@gmail.com>
> An: fop-users@xmlgraphics.apache.org
> Betreff: Re: Aw: Re: Re: Fop 1.1 / fop-pdf-images / PDFBox 1.8.3/4
> 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: powerstat@web.de
>> Bremen/Germany
>>
>>
>>
>> Gesendet: Mittwoch, 05. Februar 2014 um 11:03 Uhr
>> Von: "Luis Bernardo" <lm...@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" <lm...@gmail.com>
>>> An: "fop-users@xmlgraphics.apache.org" <fo...@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 <powerstat@web.de[powerstat@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: powerstat@web.de[powerstat@web.de]
>>> Bremen/Germany
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org[fop-users-unsubscribe@xmlgraphics.apache.org]
>>> For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org[fop-users-help@xmlgraphics.apache.org]
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
>>> For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
>> For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
>> For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
> For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
> For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
> For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
Re: Fop trunk / fop-pdf-images / PDFBox 1.8.4 -additional infos
Posted by Kai Hofmann <po...@web.de>.
I have some additional information to the NullPointerException:
- the result of pddoc.getDocument() (line 117) is Null
- the Exception only occurs when reusing the FopFactory - never during the first run.
Maybe a problem with reusing the PDFBox? I will try to have a deeper look.
Greetings
PowerStat
--
Kai Hofmann EMail: powerstat@web.de
Bremen/Germany
Gesendet: Donnerstag, 06. Februar 2014 um 13:27 Uhr
Von: "Kai Hofmann" <po...@web.de>
An: fop-users@xmlgraphics.apache.org
Betreff: Re: Fop trunk / fop-pdf-images / PDFBox 1.8.4
Dear Luis Bernadro,
I have now created a complete trunk version (fop, fop-pdf-image with pdfbox 1.8.4 (patched), xmlgraphics trunk, batik trunk).
Now I end up with the following stack trace:
Caused by: java.lang.NullPointerException
at org.apache.fop.render.pdf.pdfbox.PreloaderPDF.loadPDF(PreloaderPDF.java:117)
at org.apache.fop.render.pdf.pdfbox.PreloaderPDF.preloadImage(PreloaderPDF.java:83)
at org.apache.xmlgraphics.image.loader.ImageManager.preloadImage(ImageManager.java:176)
at org.apache.xmlgraphics.image.loader.cache.ImageCache.needImageInfo(ImageCache.java:128)
at org.apache.xmlgraphics.image.loader.ImageManager.getImageInfo(ImageManager.java:123)
at org.apache.fop.fo.flow.ExternalGraphic.bind(ExternalGraphic.java:81)
at org.apache.fop.fo.FObj.processNode(FObj.java:129)
at org.apache.fop.fo.FOTreeBuilder$MainFOHandler.startElement(FOTreeBuilder.java:289)
at org.apache.fop.fo.FOTreeBuilder.startElement(FOTreeBuilder.java:178)
at org.apache.xalan.transformer.TransformerIdentityImpl.startElement(TransformerIdentityImpl.java:1073)
at org.apache.xml.serializer.TreeWalker.startNode(TreeWalker.java:359)
at org.apache.xml.serializer.TreeWalker.traverse(TreeWalker.java:145)
at org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdentityImpl.java:390)
Do you have an idear about this?
Greetings
PowerStat
--
Kai Hofmann EMail: powerstat@web.de
Bremen/Germany
Gesendet: Donnerstag, 06. Februar 2014 um 02:12 Uhr
Von: "Luis Bernardo" <lm...@gmail.com>
An: fop-users@xmlgraphics.apache.org
Betreff: Re: Aw: Re: Re: Fop 1.1 / fop-pdf-images / PDFBox 1.8.3/4
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: powerstat@web.de
> Bremen/Germany
>
>
>
> Gesendet: Mittwoch, 05. Februar 2014 um 11:03 Uhr
> Von: "Luis Bernardo" <lm...@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" <lm...@gmail.com>
>> An: "fop-users@xmlgraphics.apache.org" <fo...@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 <powerstat@web.de[powerstat@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: powerstat@web.de[powerstat@web.de]
>> Bremen/Germany
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org[fop-users-unsubscribe@xmlgraphics.apache.org]
>> For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org[fop-users-help@xmlgraphics.apache.org]
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
>> For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
> For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
> For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
Aw: RE: Fop trunk / fop-pdf-images / PDFBox 1.8.4
Posted by Kai Hofmann <po...@web.de>.
Dear Simon Steiner,
thats no problem - as state one mail earlier the problem seems to be in context of reusing the FopFactory.
Greetings
PowerStat
--
Kai Hofmann EMail: powerstat@web.de
Bremen/Germany
Gesendet: Donnerstag, 06. Februar 2014 um 13:37 Uhr
Von: "Simon Steiner" <si...@gmail.com>
An: fop-users@xmlgraphics.apache.org
Betreff: RE: Fop trunk / fop-pdf-images / PDFBox 1.8.4
Hi,
You could check if the pdf can be read with adobe reader and pdf box
Using
java -jar pdfbox-app-x.y.z.jar PDFToImage <PDF file>
http://pdfbox.apache.org/commandline/#pdfToImage
Thanks
-----Original Message-----
From: Kai Hofmann [mailto:powerstat@web.de]
Sent: 06 February 2014 12:27
To: fop-users@xmlgraphics.apache.org
Subject: Re: Fop trunk / fop-pdf-images / PDFBox 1.8.4
Dear Luis Bernadro,
I have now created a complete trunk version (fop, fop-pdf-image with pdfbox 1.8.4 (patched), xmlgraphics trunk, batik trunk).
Now I end up with the following stack trace:
Caused by: java.lang.NullPointerException
at org.apache.fop.render.pdf.pdfbox.PreloaderPDF.loadPDF(PreloaderPDF.java:117)
at org.apache.fop.render.pdf.pdfbox.PreloaderPDF.preloadImage(PreloaderPDF.java:83)
at org.apache.xmlgraphics.image.loader.ImageManager.preloadImage(ImageManager.java:176)
at org.apache.xmlgraphics.image.loader.cache.ImageCache.needImageInfo(ImageCache.java:128)
at org.apache.xmlgraphics.image.loader.ImageManager.getImageInfo(ImageManager.java:123)
at org.apache.fop.fo.flow.ExternalGraphic.bind(ExternalGraphic.java:81)
at org.apache.fop.fo.FObj.processNode(FObj.java:129)
at org.apache.fop.fo.FOTreeBuilder$MainFOHandler.startElement(FOTreeBuilder.java:289)
at org.apache.fop.fo.FOTreeBuilder.startElement(FOTreeBuilder.java:178)
at org.apache.xalan.transformer.TransformerIdentityImpl.startElement(TransformerIdentityImpl.java:1073)
at org.apache.xml.serializer.TreeWalker.startNode(TreeWalker.java:359)
at org.apache.xml.serializer.TreeWalker.traverse(TreeWalker.java:145)
at org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdentityImpl.java:390)
Do you have an idear about this?
Greetings
PowerStat
--
Kai Hofmann EMail: powerstat@web.de Bremen/Germany
Gesendet: Donnerstag, 06. Februar 2014 um 02:12 Uhr
Von: "Luis Bernardo" <lm...@gmail.com>
An: fop-users@xmlgraphics.apache.org
Betreff: Re: Aw: Re: Re: Fop 1.1 / fop-pdf-images / PDFBox 1.8.3/4 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: powerstat@web.de
> Bremen/Germany
>
>
>
> Gesendet: Mittwoch, 05. Februar 2014 um 11:03 Uhr
> Von: "Luis Bernardo" <lm...@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" <lm...@gmail.com>
>> An: "fop-users@xmlgraphics.apache.org"
>> <fo...@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/[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
>> <powerstat@web.de[powerstat@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@166
>> d0be,
>> org.apache.xmlgraphics.image.loader.impl.ImageConverterBuffered2Rende
>> red@1127906,
>> org.apache.xmlgraphics.image.loader.impl.ImageConverterRendered2PNG@1
>> c79e64] 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@166
>> d0be] 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@166
>> d0be,
>> org.apache.xmlgraphics.image.loader.impl.ImageConverterBuffered2Rende
>> red@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: powerstat@web.de[powerstat@web.de]
>> Bremen/Germany
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> fop-users-unsubscribe@xmlgraphics.apache.org[fop-users-unsubscribe@xm
>> lgraphics.apache.org] For additional commands, e-mail:
>> fop-users-help@xmlgraphics.apache.org[fop-users-help@xmlgraphics.apac
>> he.org]
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
>> For additional commands, e-mail:
>> fop-users-help@xmlgraphics.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
> For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
> For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
RE: Fop trunk / fop-pdf-images / PDFBox 1.8.4
Posted by Simon Steiner <si...@gmail.com>.
Hi,
You could check if the pdf can be read with adobe reader and pdf box
Using
java -jar pdfbox-app-x.y.z.jar PDFToImage <PDF file>
http://pdfbox.apache.org/commandline/#pdfToImage
Thanks
-----Original Message-----
From: Kai Hofmann [mailto:powerstat@web.de]
Sent: 06 February 2014 12:27
To: fop-users@xmlgraphics.apache.org
Subject: Re: Fop trunk / fop-pdf-images / PDFBox 1.8.4
Dear Luis Bernadro,
I have now created a complete trunk version (fop, fop-pdf-image with pdfbox 1.8.4 (patched), xmlgraphics trunk, batik trunk).
Now I end up with the following stack trace:
Caused by: java.lang.NullPointerException
at org.apache.fop.render.pdf.pdfbox.PreloaderPDF.loadPDF(PreloaderPDF.java:117)
at org.apache.fop.render.pdf.pdfbox.PreloaderPDF.preloadImage(PreloaderPDF.java:83)
at org.apache.xmlgraphics.image.loader.ImageManager.preloadImage(ImageManager.java:176)
at org.apache.xmlgraphics.image.loader.cache.ImageCache.needImageInfo(ImageCache.java:128)
at org.apache.xmlgraphics.image.loader.ImageManager.getImageInfo(ImageManager.java:123)
at org.apache.fop.fo.flow.ExternalGraphic.bind(ExternalGraphic.java:81)
at org.apache.fop.fo.FObj.processNode(FObj.java:129)
at org.apache.fop.fo.FOTreeBuilder$MainFOHandler.startElement(FOTreeBuilder.java:289)
at org.apache.fop.fo.FOTreeBuilder.startElement(FOTreeBuilder.java:178)
at org.apache.xalan.transformer.TransformerIdentityImpl.startElement(TransformerIdentityImpl.java:1073)
at org.apache.xml.serializer.TreeWalker.startNode(TreeWalker.java:359)
at org.apache.xml.serializer.TreeWalker.traverse(TreeWalker.java:145)
at org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdentityImpl.java:390)
Do you have an idear about this?
Greetings
PowerStat
--
Kai Hofmann EMail: powerstat@web.de Bremen/Germany
Gesendet: Donnerstag, 06. Februar 2014 um 02:12 Uhr
Von: "Luis Bernardo" <lm...@gmail.com>
An: fop-users@xmlgraphics.apache.org
Betreff: Re: Aw: Re: Re: Fop 1.1 / fop-pdf-images / PDFBox 1.8.3/4 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: powerstat@web.de
> Bremen/Germany
>
>
>
> Gesendet: Mittwoch, 05. Februar 2014 um 11:03 Uhr
> Von: "Luis Bernardo" <lm...@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" <lm...@gmail.com>
>> An: "fop-users@xmlgraphics.apache.org"
>> <fo...@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
>> <powerstat@web.de[powerstat@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@166
>> d0be,
>> org.apache.xmlgraphics.image.loader.impl.ImageConverterBuffered2Rende
>> red@1127906,
>> org.apache.xmlgraphics.image.loader.impl.ImageConverterRendered2PNG@1
>> c79e64] 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@166
>> d0be] 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@166
>> d0be,
>> org.apache.xmlgraphics.image.loader.impl.ImageConverterBuffered2Rende
>> red@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: powerstat@web.de[powerstat@web.de]
>> Bremen/Germany
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> fop-users-unsubscribe@xmlgraphics.apache.org[fop-users-unsubscribe@xm
>> lgraphics.apache.org] For additional commands, e-mail:
>> fop-users-help@xmlgraphics.apache.org[fop-users-help@xmlgraphics.apac
>> he.org]
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
>> For additional commands, e-mail:
>> fop-users-help@xmlgraphics.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
> For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
> For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
Re: Fop trunk / fop-pdf-images / PDFBox 1.8.4
Posted by Kai Hofmann <po...@web.de>.
Dear Luis Bernadro,
I have now created a complete trunk version (fop, fop-pdf-image with pdfbox 1.8.4 (patched), xmlgraphics trunk, batik trunk).
Now I end up with the following stack trace:
Caused by: java.lang.NullPointerException
at org.apache.fop.render.pdf.pdfbox.PreloaderPDF.loadPDF(PreloaderPDF.java:117)
at org.apache.fop.render.pdf.pdfbox.PreloaderPDF.preloadImage(PreloaderPDF.java:83)
at org.apache.xmlgraphics.image.loader.ImageManager.preloadImage(ImageManager.java:176)
at org.apache.xmlgraphics.image.loader.cache.ImageCache.needImageInfo(ImageCache.java:128)
at org.apache.xmlgraphics.image.loader.ImageManager.getImageInfo(ImageManager.java:123)
at org.apache.fop.fo.flow.ExternalGraphic.bind(ExternalGraphic.java:81)
at org.apache.fop.fo.FObj.processNode(FObj.java:129)
at org.apache.fop.fo.FOTreeBuilder$MainFOHandler.startElement(FOTreeBuilder.java:289)
at org.apache.fop.fo.FOTreeBuilder.startElement(FOTreeBuilder.java:178)
at org.apache.xalan.transformer.TransformerIdentityImpl.startElement(TransformerIdentityImpl.java:1073)
at org.apache.xml.serializer.TreeWalker.startNode(TreeWalker.java:359)
at org.apache.xml.serializer.TreeWalker.traverse(TreeWalker.java:145)
at org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdentityImpl.java:390)
Do you have an idear about this?
Greetings
PowerStat
--
Kai Hofmann EMail: powerstat@web.de
Bremen/Germany
Gesendet: Donnerstag, 06. Februar 2014 um 02:12 Uhr
Von: "Luis Bernardo" <lm...@gmail.com>
An: fop-users@xmlgraphics.apache.org
Betreff: Re: Aw: Re: Re: Fop 1.1 / fop-pdf-images / PDFBox 1.8.3/4
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: powerstat@web.de
> Bremen/Germany
>
>
>
> Gesendet: Mittwoch, 05. Februar 2014 um 11:03 Uhr
> Von: "Luis Bernardo" <lm...@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" <lm...@gmail.com>
>> An: "fop-users@xmlgraphics.apache.org" <fo...@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 <powerstat@web.de[powerstat@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: powerstat@web.de[powerstat@web.de]
>> Bremen/Germany
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org[fop-users-unsubscribe@xmlgraphics.apache.org]
>> For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org[fop-users-help@xmlgraphics.apache.org]
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
>> For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
> For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
> For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
Fop trunk documentation please update
Posted by Kai Hofmann <po...@web.de>.
Hello,
while working on a migration to the latest trunk version, I found the following things are no longer correct on the website:
http://xmlgraphics.apache.org/fop/
under Versions/FOP Trunk (dev)
The "upgrading" page is completly wrong, because it still describes the upgrade from Fop-1.0 to 1.1 - should describe the upgrade from 1.1 to trunk. Most important here would be to mention that FopFactory.newInstance() no longer exists and that the Factory has to be instantiated in other ways.
under Using Apache™ FOP
The "Embed" also misses notes about FopFactory.newInstance() no longer exists also more bad is here that there are example codes that still use FopFactory.newInstance() - so the exmaples would not longer work.
The same is true for the "Servlets" page.
Because the FopFactory.newInstance() has been removed in middle of 2012 it would be very nice if someone could update the trunk documentation. Thanks in advance.
PowerStat
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
Re: Aw: Re: Re: Fop 1.1 / fop-pdf-images / PDFBox 1.8.3/4
Posted by Luis Bernardo <lm...@gmail.com>.
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: powerstat@web.de
> Bremen/Germany
>
>
>
> Gesendet: Mittwoch, 05. Februar 2014 um 11:03 Uhr
> Von: "Luis Bernardo" <lm...@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" <lm...@gmail.com>
>> An: "fop-users@xmlgraphics.apache.org" <fo...@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 <powerstat@web.de[powerstat@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: powerstat@web.de[powerstat@web.de]
>> Bremen/Germany
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org[fop-users-unsubscribe@xmlgraphics.apache.org]
>> For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org[fop-users-help@xmlgraphics.apache.org]
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
>> For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
> For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
> For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
Aw: Re: Re: Fop 1.1 / fop-pdf-images / PDFBox 1.8.3/4
Posted by Kai Hofmann <po...@web.de>.
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: powerstat@web.de
Bremen/Germany
Gesendet: Mittwoch, 05. Februar 2014 um 11:03 Uhr
Von: "Luis Bernardo" <lm...@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" <lm...@gmail.com>
> An: "fop-users@xmlgraphics.apache.org" <fo...@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 <powerstat@web.de[powerstat@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: powerstat@web.de[powerstat@web.de]
> Bremen/Germany
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org[fop-users-unsubscribe@xmlgraphics.apache.org]
> For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org[fop-users-help@xmlgraphics.apache.org]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
> For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
Re: Aw: Re: Fop 1.1 / fop-pdf-images / PDFBox 1.8.3/4
Posted by Luis Bernardo <lm...@gmail.com>.
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" <lm...@gmail.com>
> An: "fop-users@xmlgraphics.apache.org" <fo...@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 <powerstat@web.de[powerstat@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: powerstat@web.de[powerstat@web.de]
> Bremen/Germany
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org[fop-users-unsubscribe@xmlgraphics.apache.org]
> For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org[fop-users-help@xmlgraphics.apache.org]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
> For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
Aw: Re: Fop 1.1 / fop-pdf-images / PDFBox 1.8.3/4
Posted by Kai Hofmann <po...@web.de>.
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" <lm...@gmail.com>
An: "fop-users@xmlgraphics.apache.org" <fo...@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 <powerstat@web.de[powerstat@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: powerstat@web.de[powerstat@web.de]
Bremen/Germany
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org[fop-users-unsubscribe@xmlgraphics.apache.org]
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org[fop-users-help@xmlgraphics.apache.org]
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
Re: Fop 1.1 / fop-pdf-images / PDFBox 1.8.3/4
Posted by Luis Bernardo <lm...@gmail.com>.
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 <po...@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@1a966b9Converters: [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@6fe64fConverters: [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@7953f0Converters: [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@175dce3Converters: [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@f8f12cConverters: [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: powerstat@web.de
> Bremen/Germany
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
> For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
>
>