Thank you, John, I consider that. For now I intend to suggest an approach
for PDFBOX-3065 (signing using external signing service) feature
implementation. As we ourselves required it,  we used some hacks to get data
to be signed and inject the resulted signature. If PDFBox had this feature
natively , it surely could be implemented without any hacks.

With best regards,
Petras Petkus


-----Original Message-----
From: John Hewson [mailto:[email protected]] 
Sent: Thursday, August 25, 2016 9:39 PM
To: [email protected]
Subject: Re: PDFBox 2.1.0


> On 25 Aug 2016, at 03:31, Petras Petkus <[email protected]> wrote:
> 
> Most adaptation work were related to API changes, listed in 
> http://pdfbox.apache.org/2.0/migration.html
> 
> There were also many changes related to FontBox , as we used it for 
> font validation according to PDF/A-2 & 3, ex. validation of CIDSet 
> consistency
> (PDFBOX-2648 also about it).  It consumed the most time in adaptation 
> work as I had to again reread various font specifications to 
> understand whether I should report to JIRA about lost (i.e. mainly 
> hidden) features in v2.0, or it is my code which should be changed :).
> 
> For visual signatures we used the API via PDVisibleSigProperties. We 
> do not generate from text, but add graphic image in specified position 
> for signature visualization. Therefore there could be little input from
me.
> 
> We implemented signature time-stamping using Document Time Stamp 
> defined in PAdES (PDFBOX-1848 about it as well) and multiple file 
> signing using with one signing transaction (PDFBOX-3065 about it as 
> well). Probably here I could share my experience a bit.

You might want to think about contributing some of this code to PDFBox, we'd
certainly appreciate it!

-- John

> With best regards,
> Petras Petkus
> 
> 
> -----Original Message-----
> From: Maruan Sahyoun [mailto:[email protected]]
> Sent: Wednesday, August 24, 2016 6:52 PM
> To: [email protected]
> Subject: Re: PDFBox 2.1.0
> 
> Hi,
>> Am 24.08.2016 um 16:06 schrieb Petras Petkus <[email protected]>:
>> 
>> Thank you, Maruan, for response. I asked because just recently I 
>> finished migration of our tool to PDFBox v2.0. It required some 
>> adaptation work, as in some places we dealt with PDFBox internals to 
>> implement what we need (like signing multiple files, PDF/A-2 & 3 
>> validation, etc.).  Therefore was curious what would await us with 
>> v2.1
> :).
> 
> I would be very interested to understand which changes you had to do - 
> maybe some of that could be integrated in PDFBox. One thing I'll be 
> working on for
> 2.1 is appearance generation for form fields which will also include 
> signature fields.
> 
> BR
> Maruan
> 
>> 
>> Petras
>> 
>> -----Original Message-----
>> From: Maruan Sahyoun [mailto:[email protected]]
>> Sent: Wednesday, August 24, 2016 4:35 PM
>> To: [email protected]
>> Subject: Re: PDFBox 2.1.0
>> 
>> Hi,
>> 
>>> Am 24.08.2016 um 13:51 schrieb Petras Petkus <[email protected]>:
>>> 
>>> Hello,
>>> 
>>> I noticed that current PDFBox trunk has version 2.1.0, while v2.0.x 
>>> version is in separate branch. I'm curious what are main changes of
>>> v2.1
>> from v2.0?
>>> What is its status? Maybe I can read it about it? 
>>> 
>> 
>> 2.0.x is a patch release in the 2.0 series of PDFBox with no new 
>> functionality where 2.1.x includes new functions or behaviour 
>> compared to 2.0.x. In order to understand what will go into 2.1.x or 
>> is
>> (currently) planned for 2.1.x you can have a look at 
>> https://issues.apache.org/jira/browse/PDFBOX/fixforversion/12328837/?
>> s
>> electe
>> dTab=com.atlassian.jira.jira-projects-plugin:version-summary-panel
>> which lists the issues which are included in 2.1.x
>> 
>> There is also a roadmap view which lists all branches we are working 
>> on together with the issues targeted for inclusion 
>> https://issues.apache.org/jira/browse/PDFBOX/?selectedTab=com.atlassi
>> a
>> n.jira
>> .jira-projects-plugin:roadmap-panel
>> 
>> Is there something specific you are looking for?
>> 
>> BR
>> Maruan
>> 
>> 
>>> Sorry if this question was answered earlier, but I couldn't find in 
>>> mailing list.
>>> 
>>> Petras
>>> 
>>> 
>>> 
>>> --------------------------------------------------------------------
>>> - To unsubscribe, e-mail: [email protected]
>>> For additional commands, e-mail: [email protected]
>>> 
>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>> 
>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to