Download JAR files tagged by access with all dependencies

The project provides an implementation of REPOSITORY PATTERN using HIBERNATE for data access. The goal of this project is to provide an EASY TO USE API that allows to write most of CRUD operations you need in development of end user applications in ONE LINE OF CODE even for developers who are unfamiliar with Hibernate. We provide a well tested set of CRUD operations which were assembled in more than 4 years of refactoring of projects of our clients. Instead of writing same code over and over again we encourage you to try this API on your own project and see how many lines of code YOU can replace with JUST ONE LINE.

snmpAdaptor4j is an adaptor for Java Management eXtensions (JMX) providing a simple access to MBeans via the SNMP protocol. Thus, this adapter you allow to connect most monitoring tools (like Nagios and Cacti) to your Java applications. For each MBean, an XML mapping file allows to establish the relationships between attributes and the MIB of the SNMP adapter. No additional code is necessary to integrate the MBeans in the SNMP protocol. This adapter can work in a multi-applications environment (such as application servers).

The idea and motivation of the lindbergframework is to provide resources and simple solutions to problems based on the concept 'Plug and Use'. In the current version, the framework provides easy and simple solutions to the population of beans from SQL queries, abstraction of the complexities to access to stored procedures and stored functions , population of database cursors, transaction management, dependency injection, integration with Spring, JSF and Adobe Flex. The lindberg-persistence (LINP) solution, implements a important concept: separated repository of SQL commands. Among other resources.

This library aims to provide a central access point to the services exposed on the ESB without forcing each part of the system to know the actual location of the ESB and the names of the exposed endpoints. For this sake it allows to map service URI (ie referring to service in webLab taxonomy) to the actual exposed URL on the ESB within the context of a specific project. The library and the configuration should be added in portal lib in order to be central and available to any portlets. The mapping is done in a simple spring config file "webLabClient.xml" which must be accessible in JAVA classpath.

The project provides an implementation of REPOSITORY PATTERN using HIBERNATE for data access. The a goal of this project is to provide an EASY TO USE API that allows to write most of CRUD operations you will need in development of end user applications in ONE LINE OF CODE even for developers who are unfamiliar with Hibernate. We provide a well tested set of CRUD operations which were assembled in more than 4 years of refactoring of projects of our clients. Instead of writing same code over and over again we encourage you to try this API on your own project and see how many lines of code YOU can replace with JUST ONE LINE.

This project creates a bundle of the Impex legacy tool that is decoupled from Subversion. It creates a jar file that has the exact same binaries, source, directory structure, and layout as the Impex contained inside Subversion. Since it is published as a versioned jar file, it can be referenced in other processes (like the Rice binary release process) without those processes needing the ability to connect back to Subversion to check out the tool. Processes that need access to the legacy Impex tool can thus express a normal maven dependency in order to obtain it.

JBoss Rules provides an open source and standards-based business rules engine that enables easy business policy access, change and management. JBoss Rules is a fast and highly efficient rules engine that makes it easy for a business analyst or auditor to view your business rules as encoded in your IT application infrastructure to verify that the encoded rules indeed implement the documented business policies. JBoss Rules also supports a variety of language and decision table inputs, making it easy to quickly modify your business policies to respond to opportunities and competitive threats.

JBoss Rules provides an open source and standards-based business rules engine that enables easy business policy access, change and management. JBoss Rules is a fast and highly efficient rules engine that makes it easy for a business analyst or auditor to view your business rules as encoded in your IT application infrastructure to verify that the encoded rules indeed implement the documented business policies. JBoss Rules also supports a variety of language and decision table inputs, making it easy to quickly modify your business policies to respond to opportunities and competitive threats.

R can use RJava or jsr223 to communicate with java. R also has a class system called R6. If you want to use a java library with native rJava or jsr223 in R there is potentially a lot of glue code needed, and R library specific packaging configuration required. However if you don't mind writing an R-centric API in Java you can generate all of this glue code using a few java annotations and the normal javadoc annotations. This plugin aims to provide an annotation processor that writes that glue code and creates a fairly transparent connection between Java code and R code, with a minimum of hard work. The focus of this is streamlining the creation of R libraries by Java developers, rather than allowing access to arbitrary Java code from R. The ultimate aim of this plugin to allow java developers to provide simple APIs for their libraries, package their library using Maven, push it to github and for that to become seamlessly available as an R library, with a minimal amount of fuss. A focus is on trying to produce CI ready libraries tested with Github workflows and ready for CRAN submission.

Balea creates a proxy of javax.sql.DataSource, providing dynamic routing to multiple container based databases following a On Demand Data Source Access architecture. Docker is used as manager to create, start or stop database containers on demand and link correspondent data volumes. Thanks to this approach is possible to distribute data across multiple databases keeping active only the necessary ones in each moment maximizing the use of system resources. The distribution and management of data is hidden under the hood, any process that uses this data source interface (i.e. Hibernate) will perceive it as a single source of data. It makes possible for standard SQL database like Postgresql or MySQL to be maintained, backed up or versioned with simple file system operations as the data volumes are attached dynamically to the managed Docker containers. Docker integration allows also to manage database containers in remote hosts.