Johannes Katelaan commented on FOP-2526:

This is not a solution for me.

I'm using FOP embedded in a program, that creates a variety of rendered image 
formats, quite flexible, configured by the end user.

There is no fop.xconf in my software. I set all options programmatically. And 
in this case it's not anymore possible to do this. Therefore I had to add a 
copy of the TIFFDocumentHandler class to my project and change the visibility 
of the constructor myself. It works, but it should not be necessary to do this.

> TIFFDocumentHandler: change constructor visibility to protected
> ---------------------------------------------------------------
>                 Key: FOP-2526
>                 URL: https://issues.apache.org/jira/browse/FOP-2526
>             Project: FOP
>          Issue Type: Bug
>          Components: renderer/tiff
>    Affects Versions: 2.0
>            Reporter: Johannes Katelaan
>              Labels: patch
>         Attachments: FopTiffTest.java, screenshot-1.png
> The attached demo program consumes fo input an renders tif from that.
> This code is the result of migrating formerly working code from FOP 1.1 to 
> FOP 2.0.
> The class MyTiffDocumentHandler extends TIFFDocumentHandler. The call of the 
> super constructor in line 106 fails, because the constructor is not visible 
> to the derived class.
> Therefore the visibility of the constructor of TIFFDocumentHandler has to be 
> changed to protected to support this kind of usage.

This message was sent by Atlassian JIRA

Reply via email to