Charles Moulliard blogged about using Pax in ServiceMix 4:
This week, I have discovered the web possibilities offered by the ServiceMix 4 platform. SMX ("pour les intimes") uses as its core platform the excellent packages of the project PAX which is the umbrella project for all OSGi bundles and tools.
This days OSGi Alliance released the OSGi 4.2 Public Drafts. The Draft 3 contains an RFC66 named "OSGi and Web Applications" which will probably make it into a WebContainer service in the upcoming 4.2 release. The scope of this RFC is to align OSGi specs related to web development with the latest specs fo Java Servlets and Java Server Pages (JSP), which is in my opinion an excellent move pushed forward by the OSGi EEG.
The latest snapshots contain a first BETA implementation of PAXEXAM-32.
See Documentation for more.
Last week I worked on re-factoring the profiles concept.
If you would like to know more, check out the associated Jira issue
Did you ever wanted to test your bundles in a not yet released version for Felix and/or Equinox? If you use Pax Runner this is now seconds away 
. You will just have to use the snapshot version.
To startup latest deployed SNAPSHOT of Felix, which by the moment this news post was written at was 1.5.0-SNAPSHOT, use the following:
To startup the latest "Stream Stable Build" of Equinox which by the moment this news post was written at was 3.5 M5 (3.5.0.v20090127-1630), use the following:
To startup the latest snapshot build of Knopflerfish which by the moment this news post was written at was 2.2.1.snapshot_trunk_2676, use the following:
As you may know, Pax Runner caches the jars it uses, so you may run into cases where the snapshot version of the framework is not really the snapshot. To avoid that, use the option --overwriteSystemBundles. This option guarantees that the system bundles (=framework itself) wil be re-downloaded.
This feature is being tracked by http://issues.ops4j.org/browse/PAXRUNNER-203
Auto Wrap
There is now a new "--autoWrap" option in Pax Runner 0.18.0-SNAPSHOT.
If you enable it with
all your dependencies you stick into paxrunner will be gracefully checked for being a bundle (manifest+Bundle-SymbolicName must exist).
If this fails, the dependency will be wrapped using a "wrap:<yourdependency>" redirect.
Now, you can do things like that:
without careing if things are already bundles or not.
You can get a little bit more insight into what is being wrapped and what not by enabling debug logging (for the paranoid)
This is feature is being covered by http://issues.ops4j.org/browse/PAXRUNNER-211.
Java 7 Support
It is now possible to use (and test) pax runner with Java 7 execution environment.
Get it
Consider this option as IN-BETA, so give feedback if possible.
To use it, get the latest version from our snapshot repository or build it yourself from https://scm.ops4j.org/repos/ops4j/projects/pax/runner.
This is feature is being covered by http://issues.ops4j.org/browse/PAXRUNNER-212.
After last 0.3.0 release, there is now some new documentation available that should help you to get started with Pax Exam quickly:
- Pax Exam - Tutorial 1 gets you started without reading the Reference Documentation first.
- FAQ 1.x helps you to solve most known problems.
- Support tells you how to get help quickly.
Starting a couple of days ago I started rewriting the Pax Runner wiki pages. This is order to make Pax Runner easy to understand and so, to use.
So guys, be patient a couple of days. I promise it will be better.
Till then you can find the old pages here:
Pax Exam 0.3.0 has been released.
This is the first public release after the major rewrite of Pax Drone.
Special thanks to Alin Dreghiciu for much more than supporting work on this release.
Checkout release notes for details.
Pax Runner 0.17.2 has been released.
This release is a maintenance release including some minor improvements.
Checkout release notes for details.
