Introduction
We are very much excited to announce the release of first autoported version of Aspose.Pdf for Java. With this release, Aspose.Pdf for Java has become capable to create PDF files from scratch, as well as now it offers the capability to manipulate existing PDF documents; because Aspose.Pdf.Kit for Java has been merged into this product and all its classes and enumerations are now present under com.aspose.pdf.facades package. Use this single component to fulfill all your PDF related requirements.
What's New?
We did not only merge Aspose.Pdf.Kit for Java into this component, but we also have introduced a new Document Object Model (DOM). Previously it was introduced in Aspose.Pdf for .NET and to give the same leverage to our Java customers, we have ported this feature to Aspose.Pdf for Java. So now you get the capability to access PDF objects and manipulate them accordingly.
Backward compatibility
Keeping the legacy alive, in first release version, we are providing two Jar files (aspose.pdf-3.3.0.jdk1x.jar and aspose.pdf-new-4.0.0.jar). The intent of providing two jar files is to keep the migration impact as minimal as we can. In fact the current customers using legacy Aspose.Pdf for Java (versions earlier to 4.0.0 release) will continue using the same aspose.pdf-3.3.0.jdk1x.jar which only supports the creation of PDF file from scratch. However the new DOM and ported Aspose.Pdf.Kit for Java are present in aspose.pdf-new-4.0.0.jar file. Please check the following documentation topics for further details on
Future plans
Please note that in near future, we will start shipping a single jar file and the legacy Aspose.Pdf for Java (pre 4.0.0) will be ported to aspose.pdf-new-4.x.x.jar file. All the classes of legacy Aspose.Pdf for Java will become available under com.aspose.pdf.generator package. Nonetheless, the customers will only have to change class and package references in their code. But in Q3-2013, Aspose.Pdf.Kit for Java will be discontinued as separate product. Therefore we request our customers to please try using and migrating their code to new autoported release version.
Why autoported release?
Some of the customers might be thinking "why autoported release? and why they should migrate?". Well !, the quick answer is "Why don't our Java components have the same powerful set of features/functionalities as present in .NET version". I would also recommend you to please check out the following blog posts for further information on.
Training material
To quickly get started on exploring/using the features introduced in this new release version, please visit following documentation sections.
In case you encounter any issue or you find any difficulty while using features of autoported release, please do let us know and we will try our level best to get those issues resolved.
Current limitations
In first release, following features are not supported. However we plan to add these features in upcoming release versions.
- PDF to DOC conversion.
- PDF to HTML conversion.
- PDF to Tex (Latex) conversion.
- XPS to PDF conversion.
- CGM to PDF conversion.