KnowHowLab

gpsd and NMEA0183 simulator 0.1 as docker image is released

2017-05-05T16:42:00.000+02:00

Hi All,

I've released a new Docker images that helps to make tests for GPS-specific components and connectors.

How to use it:

docker run -d -p 8888:8888 -p 2947:2947 --name gpsd knowhowlab/gpsd-nmea-simulator

The started container exposes 2 ports:

8888 - raw NMEA0183 stream
2947 - gpsd service port

You can test it with:

telnet localhost 8888

gpsmon localhost:2947

KeePass Maven plugin 0.4 released

2016-04-06T12:05:00.001+02:00

A new version of KeePass Maven plugin 0.4 is available in Maven repository.

New Features:

supports both credentials: master password and key file

References:

Sources: GitHub
Documentation: User Manual
Tech documentation: Project reports
Contact: Mailing list

Thank you for your attention. Your feedback is welcome as usual.

Best Regards.

OSGi MonitorAdmin Implementation: Release 1.0.3

2016-02-14T16:33:00.000+01:00

Hello,

I'd like to announce a new release of MonitorAdmin bundle 1.0.3.

Changes:

requires Java 6+
exports org.osgi.service.monitor;version="1.0" package
requires OSGi 4.2+
logging is switched to SLF4J 1.6+

Project changes:

ported to GitHub
add Core coverage reports
Integrated with Travis CI

Maven artifact:

<dependency>
    <groupId>org.knowhowlab.osgi</groupId>
    <artifactId>monitoradmin</artifactId>
    <version>1.0.3</version>
</dependency>

Cheers,
Dmytro

Google’s J2ObjC 1.0 Translates Java into Objective-C

2016-02-06T10:34:00.001+01:00

Google’s J2ObjC 1.0 Translates Java into Objective-C: J2ObjC is an open source tool created by Google to translate Java code into corrresponding Objective-C code that can be run on iOS. The idea is to reuse Java business code between Android, web and iOS. For the web the translation is done with GWT. This tool does not deal with UI code which needs to be written separately for each platform.

Building the Internet of Things with OSGi

2016-02-02T22:24:00.000+01:00

In a world where billions of devices are being connected to the Internet, the Internet of Things (IoT) becomes an increasingly important domain. IoT offers a lot of opportunities for new and innovative applications, for example turning your home into a smart home, or turning cities into smart cities, by intelligently connecting sensor input data to various actuators.

However, with the multitude of available IoT platforms, device management protocols, wireless communication protocols, etc. it becomes hard to see the forest for the trees. In this article we will illustrate how OSGi can help us build the next generation of IoT applications.

More details...

Introduction to Nginx – Complete Tutorial

2016-02-01T17:29:00.001+01:00

Course Overview

Nginx is an open source HTTP and reverse proxy server, as well as a mail proxy server, load balancer, and HTTP cache. The nginx project started with a strong focus on high concurrency, high performance and low memory usage. It runs on Linux, BSD variants, Mac OS X, Solaris, AIX, HP-UX, as well as on other *nix flavors. It also has a proof of concept port for Microsoft Windows. According to Netcraft nginx served or proxied 17.65% busiest sites in March 2014.

This course will introduce you to the magic of nginx. You will learn to install and configure nginx for a variety of software platforms and how to integrate it with Apache.

Additionally, you will get involved with more advanced concepts like Load Balancing, SSL configuration and Websockets proxying.

More details

Amazon Announces AWS Region in Canada

2016-01-30T21:07:00.001+01:00

Amazon Announces AWS Region in Canada: Following the recent news about its South Korea region reaching general availability, Amazon has announced its plans to enter the Canadian market in 2016.

KeePass Maven plugin 0.3 released

2016-01-21T19:46:00.002+01:00

A new version of KeePass Maven plugin 0.3 is available in Maven repository.

New Features:

Group filters: name, name regex, path and UUID
Entry filters: title, title regex and UUID
Custom entry attributes
Groups/Entries duplication handling

Example:

            <plugin>
                <groupId>org.knowhowlab.maven.plugins</groupId>
                <artifactId>keepass-maven-plugin</artifactId>
                <version>0.3</version>
                <configuration>
                    <file>${project.basedir}/src/main/keepass/test.kdbx</file>
                    <password>admin123</password>
                    <jceWorkaround>true</jceWorkaround>
                </configuration>
                <executions>
                    <execution>
                        <id>read-production</id>
                        <goals>
                            <goal>read</goal>
                        </goals>
                        <configuration>
                            <records>
                                <record>
                                    <prefix>nexus.test0.</prefix>
                                    <entry>Nexus OSS</entry>
                                </record>
                                <record>
                                    <prefix>nexus.test1.</prefix>
                                    <entry>title:Nexus OSS</entry>
                                </record>
                                <record>
                                    <prefix>nexus.test2.</prefix>
                                    <entry>regex:Nexus O[S]{2}</entry>
                                </record>
                                <record>
                                    <prefix>nexus.test3.</prefix>
                                    <entry>uuid:5feb40d6feee29511f957ff791f1ec29</entry>
                                </record>
                                <record>
                                    <prefix>nexus.test4.</prefix>
                                    <entry>uuid:5feb40d6-feee-2951-1f95-7ff791f1ec29</entry>
                                </record>

                                <record>
                                    <prefix>http.test0.</prefix>
                                    <group>production</group>
                                    <entry>title:HTTP Server</entry>
                                </record>
                                <record>
                                    <prefix>http.test1.</prefix>
                                    <group>name:production</group>
                                    <entry>title:HTTP Server</entry>
                                </record>
                                <record>
                                    <prefix>http.test2.</prefix>
                                    <group>regex:pro.*tion</group>
                                    <entry>title:HTTP Server</entry>
                                </record>
                                <record>
                                    <prefix>http.test3.</prefix>
                                    <group>path:/Root/production</group>
                                    <entry>title:HTTP Server</entry>
                                </record>
                                <record>
                                    <prefix>http.test4.</prefix>
                                    <group>uuid:6f14aa86e77ad58b4e4b4f997f888a34</group>
                                    <entry>title:HTTP Server</entry>
                                </record>
                                <record>
                                    <prefix>http.test5.</prefix>
                                    <group>uuid:6f14aa86-e77a-d58b-4e4b-4f997f888a34</group>
                                    <entry>title:HTTP Server</entry>
                                </record>

                                <record>
                                    <prefix>ssh.test0.</prefix>
                                    <group>name:test</group>
                                    <entry>title:SSH Server</entry>
                                    <attributes>
                                        <attribute>
                                            <name>test_attr</name>
                                        </attribute>
                                        <attribute>
                                            <name>Manager URL</name>
                                            <mapTo>manager.url</mapTo>
                                        </attribute>
                                    </attributes>
                                </record>
                            </records>
                        </configuration>
                    </execution>
                </executions>
            </plugin>

References:

Sources: GitHub
Documentation: User Manual
Tech documentation: Project reports
Contact: Mailing list

Thank you for your attention. Your feedback is welcome as usual.

Best Regards.

KeePass Maven Plugin 0.2 released

2015-10-24T12:55:00.001+02:00

A version of KeePass Maven plugin 0.2 is available in Maven repository.

Features:

KeePass 2.x files
Filter entries by Group and Title
Publish Username, Password and URL from entry to maven properties with defined prefix
JCE workaround property (Only for Java 7 and 8)

Installation:

<plugin>
    <groupId>org.knowhowlab.maven.plugins</groupId>
    <artifactId>keepass-maven-plugin</artifactId>
    <version>0.2</version>
</plugin>

Usage:

Read Username, Password and URL from test.kdbx file, group name is production, entry title is HTTP Server and publish to Maven properties http.usrname, http.password and http.url

<plugin>
    <groupId>org.knowhowlab.maven.plugins</groupId>
    <artifactId>keepass-maven-plugin</artifactId>
    <version>0.2</version>
    <configuration>
        <file>${project.basedir}/src/main/keepass/test.kdbx</file>
        <password>admin123</password>
        <jceWorkaround>true</jceWorkaround>
    </configuration>
    <executions>
        <execution>
            <id>read-production</id>
            <phase>validate</phase>
            <goals>
                <goal>read</goal>
            </goals>
            <configuration>
                <records>
                    <record>
                        <prefix>http.</prefix>
                        <group>production</group>
                        <title>HTTP Server</title>
                    </record>
                </records>
            </configuration>
        </execution>
    </executions>
</plugin>

For Java 7 and 8 JCE should be installed. To use workaround use property <jceWorkaround>true</jceWorkaround>

References:

Sources: GitHub

Thank you for your attention. Your feedback is welcome as usual.

Best Regards.

OSGi Universal shell 1.3.0 released

2015-10-21T19:41:00.001+02:00

There is a new 1.3.0 version of OSGi universal shell adapters available.

Changes:
* moved to GitHub
* Java 6
* bug fixes for Equinox and Felix GoGo adapters
* integration tests

Command service registration with DS:

<?xml version="1.0" encoding="UTF-8"?>
<component name="shell_test.component">
    <implementation class="...ShellTestService"/>

    <service>
        <provide interface="...ShellTestService"/>
    </service>

    <property name="org.knowhowlab.osgi.shell.group.id" type="String" value="test_group_id"/>
    <property name="org.knowhowlab.osgi.shell.group.name" type="String" value="Test commands"/>
    <property name="org.knowhowlab.osgi.shell.commands" type="String">
        bndinfo#bndinfo <bundleId> - Print information for bundle with <bundleId>
        bndsinfo#bndsinfo - Print information for all bundles
    </property>
...
</component>

Maven artifacts:

<dependency>
    <groupId>org.knowhowlab.osgi.shell</groupId>
    <artifactId>equinox</artifactId>
    <version>1.3.0</version>
</dependency>

<dependency>
    <groupId>org.knowhowlab.osgi.shell</groupId>
    <artifactId>felix</artifactId>
    <version>1.3.0</version>
</dependency>

<dependency>
    <groupId>org.knowhowlab.osgi.shell</groupId>
    <artifactId>felix-gogo</artifactId>
    <version>1.3.0</version>
</dependency>

<dependency>
    <groupId>org.knowhowlab.osgi.shell</groupId>
    <artifactId>knopflerfish</artifactId>
    <version>1.3.0</version>
</dependency>

Cheers,
Dmytro

KeePass Maven Plugin 0.1 released

2015-10-19T21:07:00.000+02:00

The first version of KeePass Maven plugin 0.1 is available in Maven repository.

Features:

KeePass 2.x files
Filter entries by Group and Title
Publish Username, Password and URL from entry to maven properties with defined prefix

Installation:

<plugin>
    <groupId>org.knowhowlab.maven.plugins</groupId>
    <artifactId>keepass-maven-plugin</artifactId>
    <version>0.1</version>
</plugin>

Usage:

<plugin>
    <groupId>org.knowhowlab.maven.plugins</groupId>
    <artifactId>keepass-maven-plugin</artifactId>
    <version>0.1</version>
    <configuration>
        <file>${project.basedir}/src/main/keepass/test.kdbx</file>
        <password>admin123</password>
    </configuration>
    <executions>
        <execution>
            <id>read-production</id>
            <phase>validate</phase>
            <goals>
                <goal>read</goal>
            </goals>
            <configuration>
                <records>
                    <record>
                        <prefix>http.</prefix>
                        <group>production</group>
                        <title>HTTP Server</title>
                    </record>
                </records>
            </configuration>
        </execution>
    </executions>
</plugin>

References:

Sources: GitHub

Thank you for your attention. Your feedback is welcome as usual.

Best Regards.

OSGi Assertions and Utilities library 1.3.0 released

2015-01-08T17:14:00.001+01:00

A new version 1.3.0 of OSGi Assertions and Utilities library for integration tests is released.

Changes:

no more dependencies to JUnit API. Based on Hamcrest now
TestNG is supported now
aggregate bundle is added to simplify tests confuguration
PaxExam 3.x integration tests with JUnit and TestNG
PaxExam 4.x integration tests with JUnit and TestNG
Bug fixes and improvements

References:

Sources: GitHub
Mailing List: knowhowlab-osgi-testing

Thank you for your attention. Your feedback is welcome as usual.
Best Regards.

OSGi Assertions and Utilities library 1.2.0 released

2013-03-20T19:04:00.001+01:00

A new version 1.2.0 of OSGi Assertions and Utilities library for integration tests is released.

Changes:

EventAdmin-specific utilities and assertions

@Test
public void test_Post_Event() {
    postEvent(getBundleContext(), KNOWHOWLAB_TOPICS_TEST, 200);

    assertEvent(KNOWHOWLAB_TOPICS_TEST, 500, TimeUnit.MILLISECONDS);
}

@Test
public void test_Post_Event_With_Filters() throws InvalidSyntaxException {
    Map props = new HashMap();
    props.put("prop_key", "val123");

    postEvent(getBundleContext(), KNOWHOWLAB_TOPICS_TEST, props, 200);
    assertEvent(KNOWHOWLAB_TOPICS_TEST, FilterUtils.eq("prop_key", "val123"), 500, TimeUnit.MILLISECONDS);

    postEvent(getBundleContext(), KNOWHOWLAB_TOPICS_TEST, props, 200);
    try {
        assertEvent(KNOWHOWLAB_TOPICS_TEST, FilterUtils.eq("prop_key", "val555"), 500, TimeUnit.MILLISECONDS);
    } catch (AssertionError e) {
    }
}

ConfigurationAdmin-specific utilities and assertions

@Test
public void test_Configuration_manipulations() {
    assertConfigurationUnavailable("test.pid", null, null);

    Map config = new HashMap();
    config.put("test.key", "test.value");
    supplyConfiguration(getBundleContext(), "test.pid", null, config, 0);

    assertConfigurationUpdated("test.pid", null, null, 500, TimeUnit.MILLISECONDS);

    assertConfigurationAvailable("test.pid", null, null);

    deleteConfiguration(getBundleContext(), "test.pid", null, 0);

    assertConfigurationDeleted("test.pid", null, null, 500, TimeUnit.MILLISECONDS);

    assertConfigurationUnavailable("test.pid", null, null);
}

PaxExam 3.0.x integration tests
Bug fixes and improvements

References:

Sources: GitHub
Mailing List: knowhowlab-osgi-testing

Thank you for your attention. Your feedback is welcome as usual.
Best Regards.

OSGi integration tests with Bndtools and OSGi assertions library

2013-03-16T17:13:00.000+01:00

Introduction
Create an Integration Test project
Installing external artifacts
Add build dependencies
Write integration tests
Execute integration tests

1. Introduction

This tutorial shows you how to create OSGi integration tests with Bndtools and OSGi Assertions library. The tutorial is a continuation of the original Bndtools Tutorial.

2. Create an Integration Test project

Before start with Integration tests project please check that you finished Bndtools Tutorial and projects org.example.api and org.example.impls are created.

1. From the File menu, select New->Bndtools OSGi Project.
2. Name project org.example.it

3. Select "Integration Testing" project template

4. Edit org.example.tests.ExampleTest class to assert BundleContext

package org.example.tests;

import junit.framework.TestCase;

import org.osgi.framework.BundleContext;
import org.osgi.framework.FrameworkUtil;

public class ExampleTest extends TestCase {

    private final BundleContext context = FrameworkUtil.getBundle(this.getClass()).getBundleContext();

    public void testExample() throws Exception {
        assertNotNull(context);
    }
}

5. Right-click on org.example.it project. Run As->Bnd OSGi Test Launcher (JUnit)

3. Installing external artifacts

Now we have to install OSGi Assertions library and dependencies into local repository.
1. Select Local Repository from the list and click Add Bundles to Repository

2. Click Add Exernal JARs... and copy-paste links to artifacts:
- org.apache.servicemix.bundles.junit-4.9_2.jar
- org.knowhowlab.osgi.testing.utils-1.1.0.jar
- org.knowhowlab.osgi.testing.assertions-1.1.0.jar

4. Add build dependencies

Open org.example.test Build tab and add dependencies:
- org.example.api
- org.knowhowlab.osgi.testing.utils
- org.knowhowlab.osgi.testing.assertions
- replace junit.osgi with org.apache.servicemix.bundles.junit (to support JUnit 4.x)

5. Write integration tests

Extend ExampleTest with JUnit 4 tests and OSGi Assertions

package org.example.tests;

import java.util.concurrent.TimeUnit;

import org.example.api.Greeting;
import org.junit.Test;
import org.osgi.framework.Bundle;

import static org.knowhowlab.osgi.testing.assertions.ServiceAssert.*;
import static org.knowhowlab.osgi.testing.assertions.BundleAssert.*;
import static org.knowhowlab.osgi.testing.utils.BundleUtils.*;

public class ExampleTest {

 @Test
    public void testGreetingService() throws Exception {
        assertServiceAvailable(Greeting.class);
    }

 @Test
    public void testGreetingProvider() throws Exception {
        assertBundleState(Bundle.ACTIVE, "org.example.impls.provider");
        
        assertServiceAvailable(Greeting.class);
        
        findBundle(getBundleContext(), "org.example.impls.provider").stop();

        assertServiceUnavailable(Greeting.class, 1, TimeUnit.SECONDS);
    }
}

6. Execute integration tests

1. Update Run Requirements

2. Update Source tab and define manually test case class

3. Right-click on org.example.it project. Run As->Bnd OSGi Test Launcher (JUnit)

OSGi Assertions and Utilities library 1.1.0 released

2012-12-17T07:53:00.002+01:00

Hello,

I've released a new version 1.1.0 of OSGi Assertions and Utilities library for integration tests.

Changes:

Asynchronously change Bundle state (install, start, stop, update, uninstall) with and without delays

@Test
    public void test_Start_Bundle_Async() {
        // bundle stopped
        assertBundleState(Bundle.RESOLVED | Bundle.INSTALLED,
                          "org.knowhowlab.osgi.testing.it.test.bundle", 
                          1L, TimeUnit.MILLISECONDS);
        // start bundle in 2 sec
        startBundleAsync(getBundleContext(),  
                         "org.knowhowlab.osgi.testing.it.test.bundle", 
                         2, TimeUnit.SECONDS);
        // bundle is still stopped
        assertBundleState(Bundle.RESOLVED | Bundle.INSTALLED,
                          "org.knowhowlab.osgi.testing.it.test.bundle", 
                          1L, TimeUnit.MILLISECONDS);
        // bundle is active after 5 sec
        assertBundleState(Bundle.ACTIVE,
                          "org.knowhowlab.osgi.testing.it.test.bundle", 
                          5, TimeUnit.SECONDS);
    }

Asynchronously change Service state (register, update, unregister) with and without delays

@Test
    public void test_RegisterService_Async() {
        // service unregistered
        assertServiceUnavailable(TestService.class);
        // register service in 2 sec
        registerServiceAsync(getBundleContext(), TestService.class, 
                             new TestService(), null, 2, TimeUnit.SECONDS);
        // service still unregistered
        assertServiceUnavailable(TestService.class);
        // service registered
        assertServiceAvailable(TestService.class, 5, TimeUnit.SECONDS);
    }

Handle BundleEvents

@Test
    public void test_Bundle_Event() {
        // start bundle in 2 sec
        startBundleAsync(getBundleContext(), 
                         "org.knowhowlab.osgi.testing.it.test.bundle", 
                         2, TimeUnit.SECONDS);
        // expect bundle event within 5 sec
        assertBundleEvent(BundleEvent.STARTED,
                          "org.knowhowlab.osgi.testing.it.test.bundle", 
                          5, TimeUnit.SECONDS);
    }

Handle ServiceEvents

@Test
    public void test_Service_Event() {
        // register service in 2 sec
        registerServiceAsync(getBundleContext(), TestService.class, 
                             new TestService(), null, 2, TimeUnit.SECONDS);
        // service registered within 5 sec
        assertServiceEvent(ServiceEvent.REGISTERED, TestService.class, 
                           5, TimeUnit.SECONDS);
    }

Handle FrameworkEvents

@Test
    public void test_Framework_Event() {
        // change start level
        Executors.newSingleThreadScheduledExecutor()
                   .schedule(new Runnable() {
                             public void run() {
                                  StartLevel startLevel = 
                                  ServiceUtils.getService(getBundleContext(),
                                                          StartLevel.class);
                                  startLevel.setStartLevel(10);
                                               }
                                            }, 2, TimeUnit.SECONDS);

        // start level changed within 5 sec
        assertFrameworkEvent(FrameworkEvent.STARTLEVEL_CHANGED, 
                             0, 5, TimeUnit.SECONDS);
    }

References:

Sources: GitHub
Mailing List: knowhowlab-osgi-testing

Thank you for your attention. Your feedback is welcome as usual.
Best Regards.

OSGi Testing: make your integration/functional tests clearer. A sample with PaxExam

2012-11-04T16:22:00.000+01:00

Hello,

two years ago I've posted about small library that I used for my OSGi integration tests. During the last tree weeks I made some changes in it:

Sources were moved to GitHub
Maven groupId and artifactId were changed
Initialization process of OSGi assertions was simplified and does not require BundleContext
New utility and assertion methods for Bundles were added.

What is the difference?

You can compare two test methods that test the same functionality.

/**
     * Test bundle and service without OSGi assertions/utils
     *
     * @throws org.osgi.framework.BundleException
     *                              bundle start/stop problems
     * @throws org.osgi.framework.InvalidSyntaxException
     *                              filter creation problems
     * @throws InterruptedException wait exception
     */
    @Test
    public void test_Without_OSGiAssertions() throws BundleException, InterruptedException, InvalidSyntaxException {
        ServiceTracker packageAdminTracker = new ServiceTracker(getBundleContext(), PackageAdmin.class.getName(), null);
        packageAdminTracker.open();
        PackageAdmin packageAdmin = (PackageAdmin) packageAdminTracker.getService();
        assertNotNull(packageAdmin);
        packageAdminTracker.close();
        Bundle[] bundles = packageAdmin.getBundles("org.knowhowlab.osgi.testing.it.test.bundle", null);
        // asserts that test bundle is installed
        assertNotNull(bundles);
        // gets bundle instance
        Bundle bundle = bundles[0];
        // asserts that test bundle is resolved
        assertTrue(bundle.getState() == Bundle.INSTALLED || bundle.getState() == Bundle.RESOLVED);
        ServiceTracker serviceTracker1 = new ServiceTracker(getBundleContext(), "org.knowhowlab.osgi.testing.it.testbundle.service.Echo", null);
        serviceTracker1.open();
        assertEquals(0, serviceTracker1.size());
        // start bundle
        bundle.start();
        // asserts that test bundle is active
        assertEquals(Bundle.ACTIVE, bundle.getState());
        // asserts that test service is available within 2 seconds
        assertNotNull(serviceTracker1.waitForService(2000));
        // asserts that test service with custom properties is available
        ServiceTracker serviceTracker2 = new ServiceTracker(getBundleContext(), FrameworkUtil.createFilter(
                "(&(" + Constants.OBJECTCLASS + "=org.knowhowlab.osgi.testing.it.testbundle.service.Echo)" +
                        "(testkey=testvalue))"), null);
        serviceTracker2.open();
        assertTrue(serviceTracker2.size() > 0);
        // gets service by class and filter
        Echo echo = (Echo) serviceTracker2.getService();
        // asserts service method call
        assertEquals("test", echo.echo("test"));
        // stops bundle
        bundle.stop();
        // asserts that test bundle is resolved
        assertEquals(Bundle.RESOLVED, bundle.getState());
        // asserts that test service is unregistered
        assertEquals(0, serviceTracker1.size());
    }

    /**
     * The same Test bundle and service with OSGi assertions/utils
     *
     * @throws org.osgi.framework.BundleException
     *          bundle start/stop problems
     * @throws org.osgi.framework.InvalidSyntaxException
     *          filter creation problems
     */
    @Test
    public void test_With_OSGiAssertions() throws BundleException, InvalidSyntaxException {
        // asserts that test bundle is installed
        assertBundleAvailable("org.knowhowlab.osgi.testing.it.test.bundle");
        // asserts that test bundle is resolved
        assertBundleState(Bundle.INSTALLED | Bundle.RESOLVED, "org.knowhowlab.osgi.testing.it.test.bundle", 5, TimeUnit.SECONDS);
        // gets bundle instance
        Bundle bundle = findBundle(bc, "org.knowhowlab.osgi.testing.it.test.bundle");
        // asserts that test service is unavailable
        assertServiceUnavailable("org.knowhowlab.osgi.testing.it.testbundle.service.Echo");
        // start bundle
        bundle.start();
        // asserts that test bundle is active
        assertBundleState(Bundle.ACTIVE, "org.knowhowlab.osgi.testing.it.test.bundle");
        // asserts that test service is available within 2 seconds
        assertServiceAvailable("org.knowhowlab.osgi.testing.it.testbundle.service.Echo", 2, TimeUnit.SECONDS);
        // asserts that test service with custom properties is available
        assertServiceAvailable(and(create(Echo.class), eq("testkey", "testvalue")));
        // gets service by class and filter
        Echo echo = ServiceUtils.getService(getBundleContext(), Echo.class, eq("testkey", "testvalue"));
        // asserts service method call
        assertEquals("test", echo.echo("test"));
        // stops bundle
        bundle.stop();
        // asserts that test bundle is resolved
        assertBundleState(Bundle.RESOLVED, "org.knowhowlab.osgi.testing.it.test.bundle");
        // asserts that test service is unregistered
        assertServiceUnavailable(Echo.class);
    }

How to use the library with PaxExam

Add Maven dependencies to your integration tests pom.xml

<dependency>
            <groupId>org.knowhowlab.osgi</groupId>
            <artifactId>org.knowhowlab.osgi.testing.utils</artifactId>
            <version>1.0.0</version>
        </dependency>
        <dependency>
            <groupId>org.knowhowlab.osgi</groupId>
            <artifactId>org.knowhowlab.osgi.testing.assertions</artifactId>
            <version>1.0.0</version>
        </dependency>

Include library bundles into PaxExam tests

@Configuration
protected static Option[] baseConfiguration() {
   return options(
...
mavenBundle().groupId("org.knowhowlab.osgi").artifactId("org.knowhowlab.osgi.testing.utils").version(System.getProperty("project.version")),

mavenBundle().groupId("org.knowhowlab.osgi").artifactId("org.knowhowlab.osgi.testing.assertions").version(System.getProperty("project.version")),
...
    );
}

Use in your PaxExam integration tests:

// assert bundle with symbolic name "org.knowhowlab.osgi.testing.utils" is installed into OSGi framework
assertBundleState(Bundle.ACTIVE, "org.knowhowlab.osgi.testing.utils", 5, TimeUnit.SECONDS);
// assert bundle with symbolic name "org.knowhowlab.osgi.testing.utils" is installed into OSGi framework
assertBundleAvailable("org.knowhowlab.osgi.testing.utils");
// assert bundle with symbolic name "org.knowhowlab.osgi.testing.utils" and version "1.0.1"
// is installed into OSGi framework
assertBundleAvailable("org.knowhowlab.osgi.testing.utils", new Version("1.0.1"));
// assert bundle with symbolic name "org.knowhowlab.osgi.testing.utils" and version "2.0.0"
// is not installed into OSGi framework
assertBundleUnavailable("org.knowhowlab.osgi.testing.utils", new Version("2.0.0"));

// assert PackageAdmin service is available in OSGi registry
assertServiceAvailable(PackageAdmin.class, 5, TimeUnit.SECONDS);
// assert MonitorAdmin service is unavailable in OSGi registry
assertServiceUnavailable("org.osgi.service.monitor.MonitorAdmin");
// assert StartLevel service is available in OSGi registry
assertServiceAvailable(StartLevel.class);
// assert PackageAdmin service is available in OSGi registry
assertServiceAvailable(FilterUtils.create(PackageAdmin.class));
// assert MonitorAdmin service is unavailable in OSGi registry
assertServiceUnavailable(FilterUtils.create("org.osgi.service.monitor.MonitorAdmin"));

Here you can find the last sources of the sample.

Thank you for your attention. Your feedback is welcome as usual.
Best Regards.

OSGi universal shell implementation 1.1.0 released

2011-05-20T16:36:00.000+02:00

There is a new 1.1.0 version of OSGi universal shell adapters available.

Changes:
* Added support of defining commands services with Declarative Services

Command service registration with DS:

<?xml version="1.0" encoding="UTF-8"?>
<component name="shell_test.component">
    <implementation class="...ShellTestService"/>

    <service>
        <provide interface="...ShellTestService"/>
    </service>

    <property name="org.knowhowlab.osgi.shell.group.id" type="String" value="test_group_id"/>
    <property name="org.knowhowlab.osgi.shell.group.name" type="String" value="Test commands"/>
    <property name="org.knowhowlab.osgi.shell.commands" type="String">
        bndinfo#bndinfo <bundleId> - Print information for bundle with <bundleId>
        bndsinfo#bndsinfo - Print information for all bundles
    </property>
...
</component>

Maven artifacts:

<dependency>
    <groupId>org.knowhowlab.osgi.shell</groupId>
    <artifactId>equinox</artifactId>
    <version>1.1.0</version>
</dependency>

<dependency>
    <groupId>org.knowhowlab.osgi.shell</groupId>
    <artifactId>felix</artifactId>
    <version>1.1.0</version>
</dependency>

<dependency>
    <groupId>org.knowhowlab.osgi.shell</groupId>
    <artifactId>felix-gogo</artifactId>
    <version>1.1.0</version>
</dependency>

<dependency>
    <groupId>org.knowhowlab.osgi.shell</groupId>
    <artifactId>knopflerfish</artifactId>
    <version>1.1.0</version>
</dependency>

Cheers,
Dmytro

OSGi universal shell implementation 1.0.1 released

2011-04-02T10:44:00.000+02:00

Hi, There is a new 1.0.1 version of OSGi universal shell adapters available.

Changes:
* Changed package to org.knowhowlab.osgi.shell
* Changed maven groupId to org.knowhowlab.osgi.shell
* Added Apache Felix GoGo Universal Shell Adapter

Maven artifacts:

<dependency>
    <groupId>org.knowhowlab.osgi.shell</groupId>
    <artifactId>equinox</artifactId>
    <version>1.0.1</version>
</dependency>

<dependency>
    <groupId>org.knowhowlab.osgi.shell</groupId>
    <artifactId>felix</artifactId>
    <version>1.0.1</version>
</dependency>

<dependency>
    <groupId>org.knowhowlab.osgi.shell</groupId>
    <artifactId>felix-gogo</artifactId>
    <version>1.0.1</version>
</dependency>

<dependency>
    <groupId>org.knowhowlab.osgi.shell</groupId>
    <artifactId>knopflerfish</artifactId>
    <version>1.0.1</version>
</dependency>

Cheers,
Dmytro

OSGi Tutorial: 4 ways to activate code in OSGi bundle

2010-10-30T15:33:00.002+02:00

Hello everybody!

I would like to present a tutorial in which I show 4 ways how to activate/start code inside your OSGi bundle. All those ways are part of OSGi 4.2 specifications. The goal of the tutorial is to explain in a short form some OSGi specifications chapters with samples. I do not like to make any deep comparison of activation ways, just overview with workable examples. All sources you can find here.

Update 21.10.2013: examples were updated (Fixed an issue with missed Equinox Maven artifacts)

Contents:

Requirements. There are minimum requirements:
- Apache Maven 2.x or 3.0.x
- Your IDE with Maven support.
- Basic knowledge of OSGi specification
- Basic knowledge of PAX tools (Pax Runner). You can get some brief information also here
Use Case details. The tutorial use case is very simple:
- There is interface org.knowhowlab.osgi.tips.activation.core.Echo
```
public interface Echo {
                    String ECHO_TYPE_PROP = "echo_type";

                    String echo(String str);
                }
            
```
  This interface exported by core bundle.
- This interface should be implemented
- Implementation should be registered as OSGi service only when org.osgi.service.prefs.PreferencesService service is available in OSGi registry

Bundle Activator. This is the simplest and oldest way to activate code in your bundle.
There are some details of this activation way:

There is only one BundleActivator per bundle
Any class could implement org.osgi.framework.BundleActivator interface
This class should have empty constructor
This class should be provided with MANIFEST OSGi header Bundle-Activator to be called on OSGi bundle STARTING stage
The best way to use it (from my own experience) in low-level bundles (e.g. implementation of any OSGi API) or when you like to control everything yourself
This way could be also used when your code does not have a lot of dependencies to external services. org.osgi.util.tracker.ServiceTracker could be used to track external services. As many external services you track as more logic code you have to write to cover all cases.

Here is code of my BundleActivator that implements required tutorial use case:

public class Activator implements BundleActivator, Echo {
            // ServiceTracker for PreferencesServices
            private ServiceTracker serviceTracker;
            // BundleContext
            private BundleContext bc;
            // Registration of Echo service
            private ServiceRegistration registration;

            // activation
            public void start(BundleContext context) throws Exception {
                bc = context;
                // init and start ServiceTracker to track PreferencesService
                serviceTracker = new ServiceTracker(context, PreferencesService.class.getName(), new Customizer());
                serviceTracker.open();
            }

            // deactivation
            public void stop(BundleContext context) throws Exception {
                // stop ServiceTracker to track PreferencesService
                serviceTracker.close();
                serviceTracker = null;
            }

            public String echo(String str) {
                return str;
            }

            // customizer that handles tracked service registration/modification/unregistration events
            private class Customizer implements ServiceTrackerCustomizer {
                public Object addingService(ServiceReference reference) {
                    System.out.println("PreferencesService is linked");
                    // register Echo service
                    Dictionary<String, String> props = new Hashtable<String, String>();
                    props.put(ECHO_TYPE_PROP, "BundleActivator");
                    registration = bc.registerService(Echo.class.getName(), Activator.this, props);

                    return bc.getService(reference);
                }

                public void modifiedService(ServiceReference reference, Object service) {
                }

                public void removedService(ServiceReference reference, Object service) {
                    // unregister Echo service
                    registration.unregister();
                    System.out.println("PreferencesService is unlinked");
                }
            }
        }

Bundle MANIFEST.MF:

Manifest-Version: 1.0
        Bundle-Name: KnowHowLab Tips&Tricks: Bundle Activation - Activator
        Bundle-Version: 1.0.0.SNAPSHOT
        Bundle-ManifestVersion: 2
        Bundle-Activator: org.knowhowlab.osgi.tips.activation.activator.Activa
         tor
        Bundle-Description: KnowHowLab Tips and Tricks: Bundle Activation - Ac
         tivator
        Import-Package: org.knowhowlab.osgi.tips.activation.core,org.osgi.fram
         ework;version="1.5",org.osgi.service.prefs;version="1.1",org.osgi.uti
         l.tracker;version="1.4"
        Bundle-SymbolicName: org.knowhowlab.osgi.tips.activation.activator

Declarative Services. Declarative Services specification is the next higher-level way of activation your code in bundle. It helps developer to concentate on application logic and takes responsibility for almost all OSGi aspects of tracking and registering services.
There are some details of this activation way:

Declarative Services do not work with bundle as atomic item (as in BundleActivator way). Service Component model is used instead of Bundle model
OSGi bundle can contain any count of Service Components
Every component should have Component Description - XML file with declaration of component
Every Component Description should be listed in MANIFEST OSGi header Service-Component to be available for Service Component Runtime, that manages components and their life cycle

Here is code of my EchoComponent:

public class EchoComponent implements Echo {
            // Reference to PreferencesService
            private PreferencesService preferencesService;

            public String echo(String str) {
                return str;
            }

            // Called to bind PreferencesService
            public void bindPreferencesService(PreferencesService preferencesService) {
                System.out.println("PreferencesService is linked");
                this.preferencesService = preferencesService;
            }

            // Called to unbind PreferencesService
            public void unbindPreferencesService(PreferencesService preferencesService) {
                this.preferencesService = null;
                System.out.println("PreferencesService is unlinked");
            }
        }

Here is Component Description:

<?xml version="1.0" encoding="UTF-8"?>
        <components xmlns:scr="http://www.osgi.org/xmlns/scr/v1.0.0">
            <!-- Echo Component -->
            <scr:component enabled="true" immediate="true" name="Echo">
                <!--Component Class name-->
                <implementation class="org.knowhowlab.osgi.tips.activation.ds.EchoComponent"/>
                <!-- Echo Service description -->
                <service servicefactory="false">
                    <provide interface="org.knowhowlab.osgi.tips.activation.core.Echo"/>
                </service>
                <!-- Service registration properties -->
                <property name="echo_type" type="String" value="Declarative Services"/>
                <property name="service.pid" value="Echo"/>
                <!-- PreferencesService dependency description -->
                <reference name="preferencesService" 
                           interface="org.osgi.service.prefs.PreferencesService" 
                           cardinality="1..1"
                           policy="static" 
                           bind="bindPreferencesService" 
                           unbind="unbindPreferencesService"/>
            </scr:component>
        </components>

Bundle MANIFEST.MF:

Manifest-Version: 1.0
        Service-Component: OSGI-INF/serviceComponents.xml
        Export-Package: org.knowhowlab.osgi.tips.activation.ds;uses:="org.know
         howlab.osgi.tips.activation.core,org.osgi.service.prefs"
        Bundle-Name: KnowHowLab Tips&Tricks: Bundle Activation - DS
        Bundle-Version: 1.0.0.SNAPSHOT
        Bundle-ManifestVersion: 2
        Import-Package: org.knowhowlab.osgi.tips.activation.core,org.osgi.serv
         ice.prefs;version="1.1"
        Bundle-SymbolicName: org.knowhowlab.osgi.tips.activation.ds

There is Component Descrition annotations library that generate Component Description during OSGi bundle build and makes development of Service Components easier. Here is code with annotations:

// Component description
        @Component(name = "Echo", immediate = true)
        // Service description
        @Service(value = Echo.class)
        // Service properties
        @Property(name = Echo.ECHO_TYPE_PROP, value = "Declarative Services")
        public class EchoComponent implements Echo {
            // Reference to PreferencesService
            @Reference(name = "preferencesService", referenceInterface = PreferencesService.class,
                    cardinality = ReferenceCardinality.MANDATORY_UNARY, policy = ReferencePolicy.STATIC)
            private PreferencesService preferencesService;

            public String echo(String str) {
                return str;
            }

            // Called to bind PreferencesService
            public void bindPreferencesService(PreferencesService preferencesService) {
                System.out.println("PreferencesService is linked");
                this.preferencesService = preferencesService;
            }

            // Called to unbind PreferencesService
            public void unbindPreferencesService(PreferencesService preferencesService) {
                this.preferencesService = null;
                System.out.println("PreferencesService is unlinked");
            }
        }

Blueprint Services. Blueprint Services specification is derived from Spint Dynamic Modules specification and very similar to Declarative Services specification (developer concentrates more on application-specific code).
There are some details of this activation way:

Blueprint Services do not work with bundle as atomic item (as in BundleActivator way). Component/Bean model is used instead of Bundle model
OSGi bundle can contain any count of Components/Beans
Every component/bean should have Component Definition - XML file with definition
All Component/Bean Definitions should be stored in OSGI-INF/blueprint directory

Here is code of my EchoBean:

public class EchoBean implements Echo {
            // Reference to PreferencesService
            private PreferencesService preferencesService;

            public String echo(String str) {
                return str;
            }

            // Called to bind PreferencesService
            public void bindPreferencesService(PreferencesService preferencesService, Map props) {
                this.preferencesService = preferencesService;
                System.out.println("PreferencesService is linked");
            }

            // Called to unbind PreferencesService
            public void unbindPreferencesService(PreferencesService preferencesService, Map props) {
                this.preferencesService = null;
                System.out.println("PreferencesService is unlinked");
            }
        }

Here is Bean Definition (OSGI-INF/blueprint/echo.xml):

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
        <blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0">
            <!-- Bean definition -->
            <bean id="echoservice" class="org.knowhowlab.osgi.tips.activation.blueprint.EchoBean"/>
            <!-- Service definition -->
            <service ref="echoservice" interface="org.knowhowlab.osgi.tips.activation.core.Echo"
                     depends-on="preferencesService">
                <service-properties>
                    <entry key="ECHO_TYPE_PROP" value="Blueprint"/>
                </service-properties>
            </service>
            <!-- PreferencesService reference definition -->
            <reference id="preferencesService" interface="org.osgi.service.prefs.PreferencesService"
                       availability="mandatory">
                <reference-listener bind-method="bindPreferencesService" unbind-method="unbindPreferencesService">
                    <ref component-id="echoservice"/>
                </reference-listener>
            </reference>
        </blueprint>

I found very nice project BlueprintAnnotation under Apache Aries project. It provides runtime annotations for Blueprint beans that replaces Component/Bean Definition files. Here is EchoBean with Blueprint Annotations:

// Bean definition
        @Bean(id = "echoservice")
        // Service definition
        @Service(interfaces = Echo.class,
                serviceProperties = @ServiceProperty(key = Echo.ECHO_TYPE_PROP, value = "Blueprint-Annotations"))
        @ReferenceListener
        public class EchoBean implements Echo {
            // Reference definition 
            @Reference(availability = "mandatory", referenceListeners = @ReferenceListener(ref = "echoservice"))
            private PreferencesService preferencesService;

            public String echo(String str) {
                return str;
            }

            @Bind
            public void bindPreferencesService(PreferencesService preferencesService, Map props) {
                this.preferencesService = preferencesService;
                System.out.println("PreferencesService is linked");
            }

            @Unbind
            public void unbindPreferencesService(PreferencesService preferencesService, Map props) {
                this.preferencesService = null;
                System.out.println("PreferencesService is unlinked");
            }
        }

Web Application Bundle. Web Application Bundle (WAB) was introduced in OSGi Enterprise 4.2 Specification. WAB is a combination of JEE Web Application and OSGi bundle.
There are some details of this activation way:

WAB has the same structure as standard WAR + OSGi MANIFEST.MF
WAB uses the same life cycle and class/resource loading rules as standard OSGi bundle
WAB context path should be described in MANIFEST OSGi header Web-ContextPath
/classes and all JARs/ZIPs in /lib folder should be listed in MANIFEST OSGi header Bundle-Classpath
OSGi BundleContext is provided to WAB as ServletContext attribute "osgi-bundlecontext". It is available for Servlets/JSPs/Listeners/Filters.

Here is code of my ContextListener:

public class ContextListener implements ServletContextListener, Echo {
            private ServiceTracker serviceTracker;
            private BundleContext bc;
            private ServiceRegistration registration;

            public void contextInitialized(ServletContextEvent sce) {
                bc = (BundleContext) sce.getServletContext().getAttribute("osgi-bundlecontext");
                serviceTracker = new ServiceTracker(bc, PreferencesService.class.getName(), new Customizer());
                serviceTracker.open();
            }

            public void contextDestroyed(ServletContextEvent sce) {
                serviceTracker.close();
                serviceTracker = null;
            }

            public String echo(String str) {
                return str;
            }

            private class Customizer implements ServiceTrackerCustomizer {

                public Object addingService(ServiceReference reference) {
                    System.out.println("PreferencesService is linked");

                    Dictionary<String, String> props = new Hashtable<String, String>();
                    props.put(ECHO_TYPE_PROP, "WAB");
                    registration = bc.registerService(Echo.class.getName(), ContextListener.this, props);

                    return bc.getService(reference);
                }

                public void modifiedService(ServiceReference reference, Object service) {
                }

                public void removedService(ServiceReference reference, Object service) {
                    registration.unregister();
                    System.out.println("PreferencesService is unlinked");
                }
            }
        }

Here is web.xml:

<web-app xmlns="http://java.sun.com/xml/ns/javaee"
                 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                 metadata-complete="true"
                 version="2.5">
            <listener>
                <listener-class>org.knowhowlab.osgi.tips.activation.wab.ContextListener</listener-class>
            </listener>

            <!-- welcome file mapping -->
            <welcome-file-list>
                <welcome-file>index.htm</welcome-file>
            </welcome-file-list>
        </web-app>

Here is MANIFEST.MF:

Manifest-Version: 1.0
        Export-Package: org.knowhowlab.osgi.tips.activation.wab;uses:="org.kno
         whowlab.osgi.tips.activation.core,org.osgi.util.tracker,org.osgi.fram
         ework,javax.servlet,org.osgi.service.prefs";version="1.0.0.SNAPSHOT"
        Bundle-Classpath: WEB-INF/classes
        Bundle-Name: KnowHowLab Tips&Tricks: Bundle Activation - WAB
        Web-ContextPath: /
        Bundle-Version: 1.0.0.SNAPSHOT
        Bundle-ManifestVersion: 2
        Import-Package: javax.servlet,org.knowhowlab.osgi.tips.activation.core
         ,org.osgi.framework;version="1.5",org.osgi.service.prefs;version="1.1
         ",org.osgi.util.tracker;version="1.4"
        Bundle-SymbolicName: org.knowhowlab.osgi.tips.activation.wab

How to run examples

Download samples from here
Compile with Maven command
```
mvn clean install
```
Run BundleActivator sample
```
mvn -f run.xml -P activator
```
Run Declarative Services sample
```
mvn -f run.xml -P ds
```
Run Blueprint Services sample
```
mvn -f run.xml -P blueprint
```
Run Blueprint Annotations sample
```
mvn -f run.xml -P blueprint-annotations
```
Note: It does not work for me (even Aries BlueprintAnnotation sample). I'll try with the next version.
Run WAB sample
```
mvn -f run.xml -P wab
```

Run All sample

mvn -f run.xml -P all

Framework started:

id      State       Bundle
0       ACTIVE      org.eclipse.osgi_3.6.0.v20100517
1       ACTIVE      org.eclipse.osgi.services_3.2.100.v20100503
2       ACTIVE      org.eclipse.equinox.common_3.6.0.v20100503
3       ACTIVE      org.eclipse.equinox.preferences_3.3.0.v20100503
4       ACTIVE      org.eclipse.equinox.cm_1.0.200.v20100520
5       ACTIVE      org.eclipse.equinox.util_1.0.200.v20100503
6       ACTIVE      org.eclipse.equinox.ds_1.2.0.v20100507
7       ACTIVE      org.apache.geronimo.specs.geronimo-servlet_2.5_spec_1.2.0
8       ACTIVE      org.apache.geronimo.specs.geronimo-jaspic_1.0_spec_1.1.0
9       ACTIVE      org.eclipse.jetty.aggregate.jetty-all-server_7.2.0.v20101020
10      ACTIVE      org.eclipse.jetty.osgi.boot_7.2.0.v20101020
11      ACTIVE      slf4j.api_1.6.1
                    Fragments=12
12      RESOLVED    slf4j.jdk14_1.6.1
                    Master=11
13      ACTIVE      org.apache.aries.blueprint_0.2.0.incubating
14      ACTIVE      org.knowhowlab.osgi.tips.activation.core_1.0.0.SNAPSHOT
15      ACTIVE      org.knowhowlab.osgi.tips.activation.activator_1.0.0.SNAPSHOT
16      ACTIVE      org.knowhowlab.osgi.tips.activation.ds_1.0.0.SNAPSHOT
17      ACTIVE      org.knowhowlab.osgi.tips.activation.blueprint_1.0.0.SNAPSHOT
18      ACTIVE      org.knowhowlab.osgi.tips.activation.wab_1.0.0.SNAPSHOT

All Echo services registered:

osgi> services (objectClass=org.knowhowlab.osgi.tips.activation.core.Echo)
{org.knowhowlab.osgi.tips.activation.core.Echo}={echo_type=BundleActivator, service.id=41}
  Registered by bundle: org.knowhowlab.osgi.tips.activation.activator_1.0.0.SNAPSHOT [15]
  No bundles using service.
{org.knowhowlab.osgi.tips.activation.core.Echo}={service.pid=Echo, echo_type=Declarative Services, component.name=Echo, component.id=0, service.id=42}
  Registered by bundle: org.knowhowlab.osgi.tips.activation.ds_1.0.0.SNAPSHOT [16]
  No bundles using service.
{org.knowhowlab.osgi.tips.activation.core.Echo}={osgi.service.blueprint.compname=echoservice, ECHO_TYPE_PROP=Blueprint, service.id=46}
  Registered by bundle: org.knowhowlab.osgi.tips.activation.blueprint_1.0.0.SNAPSHOT [17]
  No bundles using service.
{org.knowhowlab.osgi.tips.activation.core.Echo}={echo_type=WAB, service.id=49}
  Registered by bundle: org.knowhowlab.osgi.tips.activation.wab_1.0.0.SNAPSHOT [18]
  No bundles using service.

Stop PersistenceService bundle, all Echo services are unregistered:

osgi> stop 3
PreferencesService is unlinked
PreferencesService is unlinked
PreferencesService is unlinked
PreferencesService is unlinked

osgi> services (objectClass=org.knowhowlab.osgi.tips.activation.core.Echo)
No registered services.

References:
1. OSGi specifications
2. OSGi API
3. Bnd tool - tool to help you diagnose and create OSGi bundles
4. maven-bundle-plugin - Maven plugin for Bnd tool
5. maven-scr-plugin - Maven plugin to ease the development of OSGi component and services
6. SCR annotations - How to use annotations for OSGi components
7. Aries Blueprint - Blueprint "Hello World" tutorial
8. Aries BlueprintAnnotations - BlueprintAnnotation tutorial
9. Pax Runner - tool to provision OSGi bundles in all major open source OSGi framework implementations (Felix, Equinox, Knopflerfish, Concierge)

Your comments are welcome.
Thank you.
Dmytro

OSGi MonitorAdmin Implementation: Release 1.0.2

2010-07-28T23:55:00.000+02:00

Hello,

I'd like to announce a new release of MonitorAdmin bundle 1.0.2. The major change - support of security permissions.

Changes:
* change POM packaging to JAR
* embed org.osgi.service.monitor package
* refactor package to org.knowhowlab.osgi.monitoradmin
* change groupId to org.knowhowlab.osgi
* change license to Apache License 2.0
* add support of security permissions
* add local permissions file

Maven artifact:

<dependency>
    <groupId>org.knowhowlab.osgi</groupId>
    <artifactId>monitoradmin</artifactId>
    <version>1.0.2</version>
</dependency>

Cheers,
Dmytro

JMX Management Model Implementation: Release 1.0.2

2010-07-09T17:56:00.000+02:00

Hi,

I'd like to announce a new minor release of JMX bundle 1.0.2.

Changes:
* refactor package to org.knowhowlab.osgi.jmx
* change groupId to org.knowhowlab.osgi
* change license to Apache License 2.0
* add support of MonitorAdmin event to notify through JMX
* handle errors on bundle start and unregister registered MBeans
* embed org.osgi.jmx package

Maven artifact:

<dependency>
    <groupId>org.knowhowlab.osgi</groupId>
    <artifactId>jmx</artifactId>
    <version>1.0.2</version>
</dependency>

Cheers,
Dmytro

Blog update

2010-07-01T17:33:00.000+02:00

Hello,

I've just moved blog from http://www.osgilab.org to http://blog.knowhowlab.org. It could be unavailable for couple of days. Hope to solve all problems with host change as soon as possible.

Sorry for inconvenience.

Best regards,
Dmytro

How to replace standard Equinox shell with Apache Felix GoGo

2010-06-28T23:09:00.002+02:00

Hello,

I've just spent some time to figure out how to integrate Apache Felix GoGo shell into Eclipse Equinox. I found two steps that should be done for this:

Disable standard Equinox shell and activate GoGo shell as default. Actually, it was not so complicated. One problem, that Equinox shell is a part of system bundle and you cannot just throw it away and replace with another implementation as you can do it with Knopflerfish. Equinox has runtime options to enable and disable console (-console, -noConsole). Then, to enable GoGo we have to install and start 3 GoGo bundles with runtime, shell and commands functionality. Fine! Now we can register shell commands based on GoGo API. Known issue: I could not replace shell when Equinox is started via Eclipse Launcher.
The second and also very important step is how to integrate Equinox shell commands into GoGo shell. I wrote some Equinox->GoGo adapter bundle that tracks Equinox shell services and registers GoGo shell service. This adapter can redirect calls from GoGo to Equinox. It can also add some usage help to Equinox commands if this help is provided by Equinox shell service.

When above steps are finished (except support of Eclipse Launcher) we can add new shell commands with GoGo and Equinox shell APIs.

Below you can find some logs from my console and the way how you can run this on your computer.

Standard Equinox Console:

osgi> help
---Controlling the OSGi framework---
 launch - start the OSGi Framework
 shutdown - shutdown the OSGi Framework
 close - shutdown and exit
 exit - exit immediately (System.exit)
 init - uninstall all bundles
 setprop = - set the OSGi property
.......

Now Equinox with GoGo console and support of Equinox shell commands

g! help
equinox:b
equinox:bundle
equinox:bundles
equinox:classSpaces
equinox:close
equinox:diag
equinox:disableBundle
equinox:disabledBundles
equinox:enableBundle
equinox:exec
equinox:exit
equinox:fork
.....
felix:start
felix:stop
felix:uninstall
felix:update
felix:which
gogo:cat
gogo:each
gogo:echo
gogo:format
gogo:getopt
gogo:gosh
......

g! help ss
ss - [-s []  []] - display installed bundles (short status)
   scope: equinox
   parameters:
      CommandSession
      String[]

g! ss -s ACTIVE
Framework is launched.
id      State       Bundle
0       ACTIVE      org.eclipse.osgi_3.6.0.v20100517
1       ACTIVE      org.apache.felix.gogo.runtime_0.6.0
2       ACTIVE      org.apache.felix.gogo.shell_0.6.0
3       ACTIVE      org.apache.felix.gogo.command_0.6.0
4       ACTIVE      org.knowhowlab.osgi.experiments.gogo.equinox_1.0.0

This solution was an experiment to integrate Apache Felix GoGo into Eclipse Equinox with support of all Equinox shell commands.
If you like to make some tests on you computer you have to download Maven project and platform definition. To start OSGi framework use command:

mvn -f demo-pom.xml

Hope, that code helps you.

Have a nice day,
Dmytro

Eclipse Equinox Helios 3.6 is out!

2010-06-23T19:01:00.000+02:00

Hello,

now we have very nice time to test our bundles and applications with 3 the most popular OSGi R4 v.4.2 frameworks: Felix, Equinox and Knopflerfish. The Equinox 3.6 was released just a few hours ago.
I've composed platform definition for Eclipse Equinox 3.6 for Pax Runned and Pax Exam.
You can download it from here or you can use it directly from POM:

<plugin>
    <groupId>org.ops4j</groupId>
    <artifactId>maven-pax-plugin</artifactId>
    <version>1.4</version>
    <configuration>
        <runner>1.4.0</runner>
        <framework>equinox</framework>
        <provision>
            <param>--log=debug</param>
            <param>--workingDirectory=target/runner</param>
            <param>--ee=J2SE-1.5</param>
            <param>--definitionURL=http://osgilab.googlecode.com/svn/trunk/org.osgilab.tips/pax-platforms/platform-equinox-3.6.0.xml</param>
        </provision>
    </configuration>
</plugin>

or from Pax Exam Unit test:

public class PaxExamTest {
   .......................
   @Configuration
    public static Option[] configurePlatform() {
        return options(
                equinox(),
                rawPaxRunnerOption("--definitionURL", "http://osgilab.googlecode.com/svn/trunk/org.osgilab.tips/pax-platforms/platform-equinox-3.6.0.xml")
        );
    }
   .......................
}

Have a nice OSGi development and testing.
Dmitriy

Knopflerfish 3.0.0 Released

2010-06-22T07:53:00.001+02:00

Hi,

This month is very rich for new OSGi framework versions. Apache Felix 3.0.0 was released a week ago and now Knopflerfish OSGi framework 3.0.0 with R4 V4.2 support is released.

What is inside:

Core specifications: Security, Module Layer, Service Layer, Life Cycle Layer - fully implemented
Framework Services: Package Admin with multihost fragments support, Start Level, Conditional Permission Admin, Permission Admin, URL Handler, Service Hooks
Service Compendium: Log, HTTP, Device Access, Configuration Admin, Meta Type, Preferences, User Admin, IO Connector, Declarative Services, Event Admin, Service and Bundle Trackers, XML Parser Service, Position, Measurement and State

A nice bunch of R4 V4.2 services :)

I've composed platform definition for Knopflerfish 3.0.0 for Pax Runned and Pax Exam.
You can download it from here or you can use it directly from POM:

<plugin>
    <groupId>org.ops4j</groupId>
    <artifactId>maven-pax-plugin</artifactId>
    <version>1.4</version>
    <configuration>
        <runner>1.4.0</runner>
        <framework>knopflerfish</framework>
        <provision>
            <param>--log=debug</param>
            <param>--workingDirectory=target/runner</param>
            <param>--ee=J2SE-1.5</param>
            <param>--definitionURL=http://osgilab.googlecode.com/svn/trunk/org.osgilab.tips/pax-platforms/platform-knopflerfish-3.0.0.xml</param>
        </provision>
    </configuration>
</plugin>

or from Pax Exam Unit test:

public class PaxExamTest {
   .......................
   @Configuration
    public static Option[] configurePlatform() {
        return options(
                knopflerfish(),
                rawPaxRunnerOption("--definitionURL", "http://osgilab.googlecode.com/svn/trunk/org.osgilab.tips/pax-platforms/platform-knopflerfish-3.0.0.xml")
        );
    }
   .......................
}

Waiting for Eclipse Helios release just to have all 3 OSGi R4 V4.2 framework implementations.

Have a nice day,
Dmitriy

KnowHowLab

gpsd and NMEA0183 simulator 0.1 as docker image is released

KeePass Maven plugin 0.4 released

OSGi MonitorAdmin Implementation: Release 1.0.3

Google’s J2ObjC 1.0 Translates Java into Objective-C

Building the Internet of Things with OSGi

Introduction to Nginx – Complete Tutorial

Amazon Announces AWS Region in Canada

KeePass Maven plugin 0.3 released

KeePass Maven Plugin 0.2 released

OSGi Universal shell 1.3.0 released

KeePass Maven Plugin 0.1 released

OSGi Assertions and Utilities library 1.3.0 released

OSGi Assertions and Utilities library 1.2.0 released

OSGi integration tests with Bndtools and OSGi assertions library

Table of Contents

1. Introduction

2. Create an Integration Test project

3. Installing external artifacts

4. Add build dependencies

5. Write integration tests

6. Execute integration tests

OSGi Assertions and Utilities library 1.1.0 released

OSGi Testing: make your integration/functional tests clearer. A sample with PaxExam

What is the difference?

How to use the library with PaxExam

OSGi universal shell implementation 1.1.0 released

OSGi universal shell implementation 1.0.1 released

OSGi Tutorial: 4 ways to activate code in OSGi bundle

OSGi MonitorAdmin Implementation: Release 1.0.2

JMX Management Model Implementation: Release 1.0.2

Blog update

How to replace standard Equinox shell with Apache Felix GoGo

Eclipse Equinox Helios 3.6 is out!

Knopflerfish 3.0.0 Released