Hi Manfred, This was a conscious decision for 2.0. By allowing subclassing, we expose the internal details of PageDrawer in our public API, which prevents us from making modifications to the internal workings of PageDrawer, which means we can’t fix bugs or make improvements which require internal refactoring.
If there’s some functionality which you feel is missing from PageDrawer, then please do let us know exactly what that is. I’m sure we can solve it more robustly without subclassing. You do say: > I need this, because i want to paint some annotation at my own. The only > thing i can to without any Pdfbox-codechanges to remove this annotations > before i render it. But I’m not sure what you mean. Are you wanting to draw specific annotations yourself, if so why? Are you unhappy with how PDFBox renders them? Can we improve that? — John > On 24 Feb 2015, at 05:23, Manfred Pock <[email protected]> wrote: > > Hi, > > why it ist not allowed to derivate or set the an own PageDrawer at the > current trunk-version of Pdfbox. > > It is not possible to derivate it because the PageDrawer is final. It's also > not possible to set the PageDrawer because he is defined fixed in PDFRenderer. > > I need this, because i want to paint some annotation at my own. The only > thing i can to without any Pdfbox-codechanges to remove this annotations > before i render it. > > Could there be a better solution. > > Regarts, Manfred > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] >
