Starting with today Pax Web has SSL (https) support.
An example can be found in the Pax Web Sample - Department Store.
Pax Web version 0.2.1-SNAPSHOT is now deployed to snapshots repository for those that do not want to build it by themselves.
To use it use the following dependency:
and the following repository:
First version (0.1.0) of Pax Web Extender has been released.
Highlights:
In the latest version of Pax-Construct I make heavy use of other maven plugins and often need to extend them with additional features or modify their behaviour. Because plexus relies on Javadoc tags to calculate the plugin metadata, you normally can't extend mojos without having the source available locally. So I developed the 'maven-inherit-plugin' which merges the local plugin metadata with metadata from any extended plugin mojos.
http://www.ops4j.org/projects/pax/construct/maven-inherit-plugin
Here's an snippet from Pax-Construct where I extend the eclipse plugin to add improved support for OSGi bundles:
Pax ConfMan consists of implementations of OSGi Configuration Admin agents, and the first release was made today. It consists of a "Properties Loader", which will populate the Configuration object from a properties file. It requires a Configuration Admin service to be present in the system. Feedback will be appreciated. Report any problems to http://issues.ops4j.org/jira/browse/CONFMAN.
OPS4J is proud to have taken one more small step towards the best logging system for OSGi, and released the 0.9.6 version. The important changes includes the change of artifactId to include "pax-logging", and that Log4J is now correctly informed about the stack composition so the "Location" format attribute shows up correctly.
If you are still using jdk 1.4 and want to use Pax Runner, from today it is possible.
Details about additions from today:
System properties (ala old runner) are now supported. See jira issues bellow and updated wiki documentation for File Scanner and Maven POM Scanner. http://issues.ops4j.org/jira/browse/PAXRUNNER-38 http://issues.ops4j.org/jira/browse/PAXRUNNER-39
Las week was dedicated to maintenance work on Pax Runner so there were not to many additions. Still to mention a few:
- Maven POM Scanner was implemented, yet not supporting pax:schema additions to pom files. If you have a pom as in the old runner just pass it in using maven protocol (mvn:group/artifact/version/pom);
- Names of the modules are now including "pax-runner-";
- Maven poms are now prepared for an eventual release;
- Wrap protocol syntax has changed;
- A new safety check on the cached bundles was added to avoid cases of a failing download.
Good news: Pax Runner is out for a day now and was already integrated in the upcoming Pax Construct.
Beside that Wrap Protocol prove it's value as there was necessary in Felix / Knopflerfish to have a bundle that exported OSGi Compendium packages and was none available in a maven repo. So, using wrap:mvn:org.osgi/osgi_R4_compendium/1.0!classpath:META-INF/platform/org.osgi.compendium.1.0.bnd did the job.
If you don't know what wrap:mvn:commons-logging/commons-logging/1.1 does you better read Wrap Protocol 
Implemented, but not yet not fully tested. Maybe you can help on testing?
If your were wondering how long it will take to implement Knopflerfish platform in the new runner, the answer is simple: less then 2 hours.
The Pax Runner 0.3.5 was released today, and marks the end of the development of that branch. The next version of Pax Runner (0.5.0) will be based on a new codebase, which has been brought into /projects/pax/runner already for those who want to try it out. See the documentation of the new Pax Runner for more information on usage. Expect a release of 0.5.0 within a couple of weeks.
Today was the maintenance days for runner so not to many new features was added. Worth mentioning is the overwrite option that lets you control if you wanna use the cached bundles (from a previous run) or overwrite them with a fresh version. You can also download a snapshot version without building it yourself.
Runner NG is now prepared to take the place of the current runner as soon as version 0.3.5 goes out.
Felix does not support a clean option. But Pax Runner does!, on Felix behalf.
Yesterday evening after a small bugs fixing section with toegether with Peter was the time for some tests on runner.
First test was to see how well runner can manage provisioning of lots of bundles. And what better place to find a lot of bundles then the plugin directory of an eclipse installation. So what do you think that happen when doing a simple command as run from within the plugin folder? Well, after a couple of seconds runner fired up Felix with over 400 bundles. Don't imagine that eclipse just showed up, it just proved the case of how easy is to provision with runner and that it can hadle large number of bunsle very fast. Only that it takes a while for Felix and Eclipse to start up with such a number of bundles.
The other test was about to prove the reusability of the modules from which reunner is build up. So, what about start eclipse with runner, provsion the platform related bundles (5.4.1. Pax Runner - Platform - Extender and 5.4.2. Pax Runner - Platform - Felix) and one Eclipse started launch felix from it? Well, just works:
pax-run scan-bundle:mvn:org.ops4j.pax.runner/platform scan-bundle:mvn:org.ops4j.pax.runner/platform-felix scan-bundle:mvn:org.ops4j.pax.runner/platform-console@nostart scan-bundle:mvn:org.ops4j.pax.runner/handler-mvn "--platform=e" "--clean" "--profiles=log"
once eclipse started and eclipse prompt is shown use the start command to start the platform-console bundle. This is a small utility that can start any installed platform. You should get a "platform>" prompt. Press "none" (ni bundles to be sinstalled) and hit enter. Ops(4j) felix started and you get the felix prompt. If you just do a "shutdown" you are back to "platform>" prompt. With "exit" you can get out of platform console and you are back in eclipse. Conclusions? Parts are reusable.
What about your zip's? Need a simple way to deploy bundles you worked so hard on? Use maven assembly plugin to put them all in a zip and provision them with runner.
Runner scans your directories! If you want so.
Checkout Directory scanner.
Two additions to runner today:
- Support to execution environments
- Bundle scanner
The page Scanner - Bundle does not exist.
Runner is now determining the provisioning schema (scanner to use) based on extension.
After some minor fixes Runner builds and runs fine under Windos / *nix, JSE5 / JSE6.
Pax Runner is the next version (0.5.0) of [Pax Runner].
As with August 21, 2007 Pax Web Extender joined Pax Web.
Pax Web Extender is a set of utilities related to web development under OSGi.
