BCL easyPDF SDK
easyPDF SDK Usermanual
PDF Creator Programming API  |  Download Free Trial  |  Contact Us to Purchase

PDFProcessor Object Description

This object represents an easyPDF PDF Processor. This is the entry point for accessing all of the easyPDF PDF Processor SDK feature. This object lets you do post-processing of existing PDF files (such as merging multiple PDF files into one, splitting one PDF file into two, and encrypting/decrypting a PDF file)

COM Object Identifiers

ProgID easyPDF.PDFProcessor.8
CLSID CBFB9F97-1258-459C-9D6B-DF7C6C36AEEF
TypeLib UUID 5DFD8A56-BCA8-4529-9A4C-25E0F743B886

Object Namespaces

COM, C++ EasyPDFProcessor
.NET COM BCL.easyPDF8.Interop.EasyPDFProcessor
Native .NET BCL.easyPDF.PDFProcessor
Java COM com.bcl.easypdf.EasyPDFProcessor.*
Native Java com.bcl.easypdf.processor.*

Example Usage (VB)

 Set oProcessor = CreateObject("easyPDF.PDFProcessor.8")
    oProcessor.Merge "input1.pdf", "input2.pdf", "output.pdf"
    

Visual C++

In modern versions of Visual C++, easyPDF Processor should be imported the following way:

#import "progid:easyPDF.PDFProcessor.8"

If you need to support multiple versions of Visual Studio, we recommend this solution:

#if _MSC_VER <= 1200 // VC6 or older
#import "c:\Program Files\Common Files\BCL Technologies\easyPDF 8\bepproc.dll"
#else
#import "progid:easyPDF.PDFProcessor.8"
#endif

Native .NET API

There is now a 100% native .NET API for easyPDF Processor, which is strongly recommended over the traditional COM objects.

All native .NET declarations and sample code have a light yellow background color, like this:

PDFProcessor processor = new PDFProcessor();
try
{
   int numberOfPages = processor.GetPageCount(@"c:\test\input.pdf");
   Console.WriteLine(numberOfPages);
}
catch(PDFProcessorException e)
{
   Console.WriteLine(e.Message);
}

The PDFProcessor class does not have a Dispose() method, it is simply garbage collected. Each member function inside PDFProcessor launches an individual external worker process. Even if a function throws, the external process quits automatically.

The PDFProcessorHandle class, on the other hand, has a Dispose() method, and it is mandatory to call it for each object when they are not used anymore. A single external worker process is launched for each instance of PDFProcessorHandle. Each worker process quits when Dispose() is called explicitly by the user.

Native Java API

There is now a 100% native Java API for easyPDF Processor, which is strongly recommended over the traditional JACOB Java COM bridge.

All native Java declarations and sample code have a light red background color, like this:

PDFProcessor printer = new PDFProcessor();
try
{
   int numberOfPages = processor.GetPageCount("c:\\test\\input.pdf");
   System.out.println(numberOfPages);
}
catch(PDFProcessorException e)
{
   System.out.println(e);
}

The PDFProcessor class does not have a dispose() method, it is simply garbage collected. Each member function inside PDFProcessor launches an individual external worker process. Even if a function throws, the external process quits automatically.

The PDFProcessorHandle class, on the other hand, has a dispose() method, and it is mandatory to call it for each object when they are not used anymore. A single external worker process is launched for each instance of PDFProcessorHandle. Each worker process quits when Dispose() is called explicitly by the user.