Download JAR files tagged by started with all dependencies

Essencium-backend-uuid-model is a software library built on top of Essencium Backend that allows developers to quickly get started on new software projects. Essencium provides, for example, a fully implemented role-rights concept as well as various field-tested solutions for access management and authentication. Essencium Backend UUID Model uses UUID's as primary keys in relational databases and delivers a fully implemented App-User.

Essencium Backend is a software library built on top of Essencium Backend that allows developers to quickly get started on new software projects. Essencium provides, for example, a fully implemented role-rights concept as well as various field-tested solutions for access management and authentication. The Storage Module can be used as a plugin to store files to al local folder or some other storage providers (e.g. S3).

This bundle acts as an agent for the remote launching architecture. When started, it will bind to port 29998 and listens for incoming requests. When this port is accessed, it will open a link that allows it to act as an OSGi management agent that is remotely controlled. When this connection is closed, it will remove all bundles that were installed through this connection. The protocol is highly optimized to make this also work for small devices and slow connections.

Inkremental is a small library for creating reactive user interfaces. Originally inspired by React, it suits well as a view layer for MVVM or Redux design patterns. Started as a fork of Java library Anvil, it is fully rewriten in Kotlin, with many improvements pulled in and more to come!

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.

A plugin for the Apache Felix Webconsole. When installed, this bundle will add a tab on the Web Console that provides a graphic overview of the OSGi framework, including services, bundles, and components. Colors are used to encode the different states. Bundles are shown to be started, stopped, starting, resolved, and installed. Services are shown to be used, looked for, or registered in the air. Components can be seen to be operating or not satisfied. Most objects have a tooltip with extra information and all objects can be clicked upon. Hovering over a bundle or service shows only the conenections to/from the component. The display updates every 5 seconds to provide a continuous view on the operations of the framework it runs on.

Bundle with a synchronous activator which will install OGEMA resources from XML (.ogx) or JSON (.ogj) files located in config/resources (default). This requires a running OGEMA framework when the bundle is started and enables the installation of basic resources before other applications are activated. Also adds a service for felix fileinstall that will install such resource files. Files installed through fileinstall will be reinstalled when they are updated or when a newer version of an installed file is found after a restart (using the file's last modification timestamp). Files installed from the configuration directory will only be reinstalled on a restart, if they have been changed.

A plugin for the Apache Felix Webconsole. When installed, this bundle will add a tab on the Web Console that provides a graphic overview of the OSGi framework, including services, bundles, and components. Colors are used to encode the different states. Bundles are shown to be started, stopped, starting, resolved, and installed. Services are shown to be used, looked for, or registered in the air. Components can be seen to be operating or not satisfied. Most objects have a tooltip with extra information and all objects can be clicked upon. Hovering over a bundle or service shows only the conenections to/from the component. The display updates every 5 seconds to provide a continuous view on the operations of the framework it runs on.

Oxalis integration test. Compiles and packages everything, after which the web container is started in the pre-integration-test phase, the .war file is deployed and the tests are executed in the integration-test phase. After the tests have been executed, the web container is stopped in the post-integration-test phase. The reason for using failsafe is the fact that Surefire would fail the build in the integration-test phase, without taking down the server in the post-integration-test phase. This implementation uses Tomcat, but you may change this to your liking. See http://cargo.codehaus.org/Maven2+plugin for more information.

ATG DUST is a framework for building JUnit tests for applications built on the ATG Dynamo platform. This framework allows one to quickly write test code that depends up Nucleus or ATG Repositories. By using this framework one can drastically cut down on development time. It takes only a few seconds to start up a test with a repository, but it may take multiple minutes to start up an application server. To get started with DUST, take a look at http://atgdust.sourceforge.net/first-test.html. This page will walk you through the process of running a basic test which starts Nucleus. After that, read the other getting started guides to describe how to create standalone Junit tests which can startup repositories and use the DynamoHttpServletResponse classes. For only ATG10 and tested.