Download JAR files tagged by service with all 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.

This bundle wraps Pi4j (http://pi4j.com) that wraps the native code Wiring Pi (http://wiringpi.com). It wraps these libraries to make them OSGi friendly and allow them to work together with the OSGi enRoute IoT circuit library (osgi.enroute.iot.circuit). The bundle will first use Pi4J to detect on what hardware it runs. If it runs on an appropriate type, it will register a component that can be configured with Metatype. The Metatype defines a full blown configuration template for all the Pi's functions. The GPIO's are registered as components for the circuit. Regardless of the success of the configuration, this bundle will also register a GpioController service, which is the main Pi4J class.

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.

This is a simple Web Service Client library to call wide variety of web service behind HTTP. In theory it can support any interface or payload. On the request side, to convert java object to HTTP request components (URL, headers, body), templating is used which allows it to call XML, JSON, SOAP, REST or anyother custom interface. On the response side, it uses pluggable parser and a mapper to only extract the fields that are of interest for the client program. The parser currently supports JSON and XML and returns a collections tree.

This module provides access to the set of utility classes required to interact with an instance of an AppWorks Gateway from an AppWorks Service. It covers AppWorks dedicated service deployment API, which is a limited subset of the full AppWorks admin API. We currently provide the facility for services to listen to service life-cycle events such as 'service installed', 'service upgraded' and 'service uninstalled'. We also provide the facility for centralised configuration setting management. As AppWorks services are edited from the AppWork Gateway administration console, we provide the ability to respond to updates made here, and also expose creation and update end points for these settings.

This is CRUD interface based on standard JEE MVC servlet, JSP, JSTL. It renders forms and lists of any entity according XML settings (Beige-Settings). Database logic is handled by Beige-ORM. It also includes Mail-sender and database replicator through WEB-service. It is SQLite configured. Put WAR file into Tomcat7 webapps, make sure that Tomcat has libraries: HikariCP-2.4.3.jar, sqlite-jdbc-3.8.11.2.jar, slf4j-api-1.7.12.jar (versions may be different), for MS Windows change file separator in META-INF\context.xml connectionURL from "/" to "\" and reassemble WAR. Beigesoft-Accounting-Web extends it into very complex business application.

Tool used to analyze a set of classes and determine on what other classes they directly or indirectly depend. Typically this tool is used to compute the necessary and sufficient set of classes to include in a JAR file, for use in the class path of a client or service, or for use in the codebase of a client or service. The tool starts with a set of "root" classes and recursively computes a dependency graph, finding all of the classes referenced directly by the root classes, finding all of the classes referenced in turn by those classes, and so on, until no new classes are found or until classes that are not of interest are found. The normal output of the tool is a list of all of the classes in the dependency graph. The output from this command can be used as input to the jar tool, to create a JAR file containing precisely those classes.

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.

This bundle wraps Pi4j (http://pi4j.com) that wraps the native code Wiring Pi (http://wiringpi.com). It wraps these libraries to make them OSGi friendly and allow them to work together with the OSGi enRoute IoT circuit library (osgi.enroute.iot.circuit). The bundle will first use Pi4J to detect on what hardware it runs. If it runs on an appropriate type, it will register a component that can be configured with Metatype. The Metatype defines a full blown configuration template for all the Pi's functions. The GPIO's are registered as components for the circuit. Regardless of the success of the configuration, this bundle will also register a GpioController service, which is the main Pi4J class.