Hello again. Thanks again to Jeremias's invaluable help. Much
appreciated. I believe the issue is now resolved. For the benefit of
everyone else here is a summary of what I did:
1. Set up the listener, adaptor and producer:
- Added 'void warnRevision3PermissionsIgnored(Object source);' (and
Thanks again Jeremias. Your help much appreciated.
I have made the PDFEncryptionJCE class pass itself as source into
PDFEventListener.warnRevision3PermissionsIgnored() which gets passed
onto the PDFEventProducer.
Yes I am indeed calling
PDFEventListener.warnRevision3PermissionsIgnored()
On 13.05.2011 17:06:56 Michael Rubin wrote:
Thanks for your reply. I have now added the getter and setter to
PDFDocument as shown below and added 'this.pdfDoc.setEventListener(new
PDFLibraryEventAdapter(getUserAgent().getEventBroadcaster());' to
PDFDocumentHandler.startDocument() (last line
Thanks for your reply. I have now added the getter and setter to
PDFDocument as shown below and added 'this.pdfDoc.setEventListener(new
PDFLibraryEventAdapter(getUserAgent().getEventBroadcaster());' to
PDFDocumentHandler.startDocument() (last line inside the try block). Now
I can get the
Thanks a lot for your response Jeremias. I have now done the following:
- Added 'void warnRevision3PermissionsIgnored(Object source);' (and its
javadoc) to PDFEventProducer in the org.apache.fop.render.pdf package and added
a corresponding entry to the xml. Removed the
On 12.05.2011 10:44:41 Michael Rubin wrote:
Thanks a lot for your response Jeremias. I have now done the following:
- Added 'void warnRevision3PermissionsIgnored(Object source);' (and its
javadoc) to PDFEventProducer in the org.apache.fop.render.pdf package and
added a corresponding entry
Hello there. I have been busy implementing 128 bit PDF encryption for FOP. I
have already got it working successfully but one issue remains that I have a
question about.
In the org.apache.fop.pdf.PDFEncriptionJCE.init() method there is one place where I want
to broadcast an event message. I
Hi Michael
Creating a new EventBroadcaster is obviously wrong. The idea is that the
user can get events for each FOP rendering run separately (unlike
logging where concurrent runs get mixed up). So you have to get hold of
that EventBroadcaster applicable to the current rendering run. Obviously,
