Download JAR files tagged by looking with all dependencies

Metro is a high-performance, extensible, easy-to-use web service stack. It is a one-stop shop for all your web service needs, from the simplest hello world web service to reliable, secured, and transacted web service that involves .NET services. This module is exclusively meant for use in GlassFish V3 development. It is highly unlikely to work in any other environment. If you are looking for a Maven distribution of Metro, please use com.sun.xml.ws.webservices.

AuelProject DataSift is a data validation and transformation framework built on top of the J2SE platform which mainly targets enterprise applications, creating an environment where data validation and transformation can be done in a simplistic yet powerful way. It allows the developer to create plugins for both looking for the data to be validated (resolving) and validating or transforming it.

Fontys Venlo best maven practices. "Up with your competencies" The 'testeasypom' Parent pom that provides all dependencies that you need for modern testing, generating good looking Javadoc and a set of static test reports using spotbugs, pmd, and checkstyle. This is NOT cargo-cult, because NONE of the dependencies in this pom will end up in your final product. This is a continuation of sebipom. Version 4.0.7: update dep and plugin versions. Version 4.0.8: jacaco 0.8.8 for java 17 and 18 support Version 4.0.11: default to java 17 Version 5.1.0: default to java 21 Version 5.2.0: include testfx stuff in fx profile

This powerful reporting library aims to simplify producing reports using iText. Looking at producing reports with iText the most demanding tasks are how to get from data to report blocks, how to style those blocks and how to evaluate (debug) the resulting report. Exactly those three major tasks are well supported by the VectorPrint report library: - (combination of) xml configuration and annotations to transform existing Java data objects into report block - provide styling information (css like) seperate from code - a firebug like debug mode to help evaluate your report.

This project is a GUI utility for processing files. It allows selecting a set of source files and a pipeline of processes to apply onto those files. The applications shows in a nice-looking user interface where you can define profiles for your repetitive tasks. It provides pre-defined processors doing usual file manipulation tasks like: Copy, Head, Tail, Chunk, Search, Replace, Zip, Unzip... But the biggest value of this file processor tool is the ability to add easily custom file processors written in java.

Spring LDAP is a Java library for simplifying LDAP operations, based on the pattern of Spring's JdbcTemplate. The framework relieves the user of common chores, such as looking up and closing contexts, looping through results, encoding/decoding values and filters, and more. The LdapTemplate class encapsulates all the plumbing work involved in traditional LDAP programming, such as creating a DirContext, looping through NamingEnumerations, handling exceptions and cleaning up resources. This leaves the programmer to handle the important stuff - where to find data (DNs and Filters) and what do do with it (map to and from domain objects, bind, modify, unbind, etc.), in the same way that JdbcTemplate relieves the programmer of all but the actual SQL and how the data maps to the domain model. In addition to this, Spring LDAP provides transaction support, a pooling library, exception translation from NamingExceptions to a mirrored unchecked Exception hierarchy, as well as several utilities for working with filters, LDAP paths and Attributes.

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.