Download JAR files tagged by javax with all dependencies

OSGi bundle that contains the JDBC API coming from OpenJDK 1.7. In case of OSGi, it is better to exclude javax.sql.*, com.sun.rowset.* and javax.transaction.* packages from the boot classpath and use them from bundles. Very often javax.transaction.* packages are used from a custom bundle. As javax.sql.XADataSource wires to that package, it is logical to have that in a custom bundle as well so there will be no package wiring issues.

Extension for Jackson (http://jackson.codehaus.org) to offer alternative support for serializing POJOs as XML and deserializing XML as pojos. Support implemented on top of Stax API (javax.xml.stream), by implementing core Jackson Streaming API types like JsonGenerator, JsonParser and JsonFactory. Some data-binding types overridden as well (ObjectMapper sub-classed as XmlMapper).

This is a generic WebLab portlet developed for the WebLab platform. It eases development if multiple events need to be handled. Please note that some libraries need to be provided by the portal. Some provided libraries are probably in the portal own libraries (javax.portlet:portlet-api, javax.servlet:servlet-api, javax.servlet:jstl and taglibs:standard). Some other need to be added by your own (for eventing), they are WebLab specific, since we encourage you to only exchange objects of the WebLab model as events (org.weblab-project.core:model, org.weblab-project.core:extended).

Skeletal implementation of interface javax.lang.model.util.Types, plus concrete realization backed by core Java Reflection API, akin to JEP 119. This module implements those methods in interface javax.lang.model.util.Types that pertain to the Java type system, plus it provides a method for resolving formal type parameters to actual type arguments. These methods have no equivalent in the Java Reflection API. The abstract skeletal implementation in this module is meant to be specialized for a particular javax.lang.model implementation. The abstraction makes this module well-suited to be used in projects that contain javax.lang.model as part of their domain model (for instance, implementations of alternative languages on top of the JVM).

JSci is a set of open source Java packages. The aim is to encapsulate scientific methods/principles in the most natural way possible. As such they should greatly aid the development of scientific based software. It offers: abstract math interfaces, linear algebra (support for various matrix and vector types), statistics (including probability distributions), wavelets, newtonian mechanics, chart/graph components (AWT and Swing), MathML DOM implementation, ... Note: some packages, like javax.comm, for the astro and instruments package aren't listed as dependencies (not available).

This is a generic parent POM for some portlet developed for the WebLab platform by EADS team members. For some needs we developed the Abstract WebLab Portlet. It eases development if multiple events need to be handled. If you do not need these functionalities, please consider using an other parent POM for you portlet instead of this POM. Please note that some libraries need to be provided by the portal. Some provided libraries are probably in the portal own libraries (javax.portlet:portlet-api, javax.servlet:servlet-api, javax.servlet:jstl and taglibs:standard). Some other need to be added by your own (for eventing), they are WebLab specific, since we encourage you to only exchange objects of the WebLab model as events (org.weblab-project.core:model, org.weblab-project.core:extended).

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.