Download JAR files tagged by limitations with all dependencies

A Maven plugin for generating a BeanFactory from a Spring application context. In order to work around the limitations on platforms not supporting reflection, this Maven plugin will analyze the sources and dependent jar files to gather all the required information at build time.

An open library used to connect to the ecFeed service. It can be also used as a standalone testing tool. It is integrated with Junit5 and generates a stream of test cases using a selected algorithm (e.g. Cartesian, N-Wise). There are no limitations associated with the off-line version but the user cannot access the on-line computation servers and the model database.

An implementation of missing spring data repository hooks. JPA @EventHandlers have following limitations, which have been solved in this library: 1) It leads to circular dependency between your entity and it's event handler which makes it impossible to split your application into dedicated modules or extends an existing one with own modules. 2) The inability to inject spring beans without using of static context.

The JavaFX Deploy Lib provides a core functionality for assembling JavaFX applications. It is build-tool independent and is intended to be used as a base to build plugins for Maven, Gradle and other third party tools. It is a direct replacement for the 'JavaFX packaging' library that comes with the JDK but without the limitations that come from being bundled in the JDK.

Spring Batch archetypes are simple project templates containing just enough code to get you started running a job. For more detailed examples of using particular features of the framework, look at the Spring Batch Samples project. Currently the archetypes are deployed as regular Maven projects (not archetypes), because of limitations in the archetype plugin (or our understanding of how it works). For most effective use, copy one into Eclipse and use Q4E to manage the dependencies.

Programmatically generate, load, modify, and convert Excel .xlsx spreadsheets in your Java applications. Document Solutions for Excel (DsExcel, previously GcExcel) is a cross-platform high-speed, small-footprint spreadsheet API library that requires no dependencies on Excel. The powerful calculation engine supports 450+ Excel Functions and custom functions to perform complex calculations. DsExcel is 2x+ faster and uses less memory than Apache POI and allows you to save to XLSX, PDF, HTML, CSV, JSON and Images. Deploy your applications to the cloud, Windows, Mac, or Linux. If you'd like to remove the trial watermark and other trial limitations, please email [email protected] to request your 30-day evaluation key.

Programmatically generate, load, modify, and convert Excel .xlsx spreadsheets in your Java applications. GrapeCity Documents for Excel (GcExcel) is a cross-platform high-speed, small-footprint spreadsheet API library that requires no dependencies on Excel. The powerful calculation engine supports 450+ Excel Functions and custom functions to perform complex calculations. GcExcel is 2x+ faster and uses less memory than Apache POI and allows you to save to XLSX, PDF, HTML, CSV, JSON and Images. Deploy your applications to the cloud, Windows, Mac, or Linux. If you'd like to remove the trial watermark and other trial limitations, please email [email protected] to request your 30-day evaluation key.

GroupDocs.Signature for Java allows developers to write applications with ability to significantly sign electronic docs and verify them. Signatures can be of different types. API supports multitude of file formats and includes Pdf, Microsoft Office documents, Open Office formats, PowerPoint presentations, Images etc. The quite captivating fact about the API is, its UI less and independent calls can be made. It also provides a useful features to verify signed documents with stored signatures. Signature Types: - Text Signature - Image Signature - Digital Signature - Barcode Signature - QR-Code Signature - Stamp Signature Verification Types: - Text Signature - Digital Signature - Barcode Signature - QR-Code Signature For more details on the library, please visit GroupDocs website at: http://groupdocs.com/products/signature/java Note: The library comes up with some limitations in the evaluation mode. In order to test full features of GroupDocs.Signature for Java library, please request a free 30-day temporary license.

GroupDocs.Metadata for Java is a class library to process metadata associated with various Document, Image, CAD, Audio, Video and Archive formats. Key Features: - Covers most popular metadata standards: XMP, EXIF, IPTC, Image Resource Blocks, ID3, document properties - Covers most popular document formats: Microsoft Word, Microsoft Excel, Microsoft PowerPoint, PDF, Microsoft OneNote, Microsoft Visio, Open Document Format - Covers most popular image formats: BMP, GIF, DjVu, JPEG, PNG, TIFF, PSD, WebP, WMF, EMF, DICOM - Covers most popular email formats: Outlook Message, Email Message - Covers most popular audio formats: Mp3, WAV - Covers most popular video formats: Avi, Mov - Create, modify and remove metadata associated with supported document and image formats with a few lines of code - Manage EXIF metadata in Jpeg and TIFF formats - Manage XMP metadata in image and PDF formats - Manage Image Resource blocks in image formats - Manage audio metadata: ID3 tag (ID3v1, ID3v2), Lyrics3 tag, APE - Utilities to inspect and clean hidden metadata in document formats - Utilities to Search and Compare all metadata - Utilities to Export metadata to Excel/Csv - Metadata cleaner utility - MIME type detection - Read track changes. Accept or reject track changes - Read EXIF maker-notes: Sony, Nikon, Canon, Panasonic For more details on the library, please visit GroupDocs website at: https://products.groupdocs.com/metadata/Java Note: The library comes up with some limitations in the evaluation mode. In order to test full features of GroupDocs.Metadata for Java library, please request a free 30-day temporary license.

The OODT grid services (product and profile services) use CORBA or RMI as their underlying network transport. However, limitations of CORBA and RMI make them inappropriate for large-scale deployments. For one, both are procedural mechanisms, providing a remote interface that resembles a method call. This makes streaming of data from a service impossible, because there are limitations to the sizes of data structures that can be passed over a remote method call. Instead, repeated calls must be made to retrieve each block of a product, making transfer speeds horribly slow compared to HTTP or FTP. (Block-based retrieval of profiles was never implemented, resulting in out of memory conditions for large profile results, which is another problem.) Second, both CORBA and RMI rely on a central name registry. The registry makes an object independent of its network location, enabling a client to call it by name (looking up its last known location in the registry). However, this requires that server objects be able to make outbound network calls to the registry (through any outbound firewall), and that the registry accept those registrations (through any inbound firewall). This required administrative action at institutions hosting server objects and at the institution hosting the registry. Often, these firewall exceptions would change without notice as system adminstrators changed at each location (apparently firewall exceptions are poorly documented everywhere). Further, in the two major deployments of OODT (PDS and EDRN), server objects have almost never moved, nullifying any benefit of the registry. This project, OODT Web Grid Services, avoids the prolems of CORBA and RMI by using HTTP as the transport mechanism for products and profiles. Further, it provides a password-protected mechanism to add new sets of product and profile query handlers, enabling seamless activation of additional capabilities.