As the topic suggests, I noticed that the PdfFileEditor.setAllowConcatenateExceptions is deprecated. So is it not safe to set this flag anymore? Should I avoid it using it at all?
Thanks for the report. I have not confirmed this yet and can only confirm it after reproducing on our side. I need a bit more information to answer precisely for Aspose.Pdffileeditor.
- Which version of Aspose.PDF for Java are you currently using?
- Are you encountering any specific issues or exceptions when you try to use
setAllowConcatenateExceptions?
A support engineer will review your answers and follow up in this thread.
Once I have the missing details, I’ll try to reproduce this. If I can confirm it, I’ll log it internally and follow up here.
A support engineer will follow up in this thread if needed.
I am using Aspose.PDF 25.4
I just wonder why it is deprecated and if it is unsafe to use this deprecated method.
Cuz without setting this flag, the only information from PdfFileEditor.concatenate is success or not, without providing the users with the reasons of failure.
Thanks!
Thanks for the sample file(s); that should help with reproduction. I have not confirmed this yet and can only confirm it after reproducing on our side. I need a bit more information to answer precisely for Aspose.PDF when converting pdf to unknown.
- Are you currently experiencing any runtime errors or unexpected behavior when calling
setAllowConcatenateExceptionsin version 25.4? - What specific functionality are you relying on from this method (e.g., handling of concatenation errors in a particular workflow)?
A support engineer will review your answers and follow up in this thread.
I’ll try to reproduce this using your samples. If I can confirm it, I’ll log it internally and follow up here.
A support engineer will follow up in this thread if needed.