Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 22 Next »

Unknown macro: {ops4j-style-page}

What version of java is required by Pax Runner?

Pax Runner is targeting Java 5.0 and beyond but a Java 1.4 compatible version is also available. See details.

Are there any examples of how to use Pax Runner options?

Yes, see details.

I'm using Pax Construct. How can I make use of Pax Runner?

[Pax Construct] uses Pax Runner under the hood when using pax-provision (script and maven pax plugin pax:construct goal). By using this bundles from your project are deployed to the target platform. See [Pax Construct] for details.

I'm using Spring DM (Spring OSGi). Is Pax Runner of any use?

Pax Runner will help you first of all to start up your bundles on all supported platforms. In plus Pax Runner has some extra features for Spring DM users. [Read about them.]

I'm using spring-dm profile. What version of Spring DM I get to use?

Pax Runner is using the latest released version of Spring DM at all times. So, as soon as Spring DM releases a new version that version will be automatically downloaded and used.

My application has a dependency on a "classic" jar. How can I use it?

To be able to use your jar in osgi, the jar's manifest must have at least some mandatory osgi headers. You can archive this goal in many ways as by adding the entries by yourself, using bnd, maven-bundle-plugin or [Pax Construct]. In all of this ways you will be able to ransform the "classic" jar into an OSGi bundle. But all of them are doing it at build time. By using the [wrap: protocol] you will be able to transform the jar into a bundle at runtime. [See details].

I have to set some framework properties. How can I do that?

Let's take for example the case when you want to set the property org.osgi.service.http.port=8080
You can archive this in different ways depending on your case:

  • using [File Scanner] provisioning
  • using [Maven 2 POM Scanner] provisioning
  • using a system property as defined by OSGi specs for BundleContext.getProperty:

    If the key is not found in the Framework properties, the system properties are then searched.

I want to use the same kind of urls in the targeted framework as used when starting Pax Runner. Is that possible?

Yes, that was always possible. And starting with Pax Runner version 0.8.0 it becomes much simpler as new profiles were added to support this. Now you just have to use the url or url+obr profile, as for example in:

pax-run --profiles=url

I'm using Pax Runner on DOS/Windows, I have the right command but I'm getting strange errors

DOS/Windows shell seems to strip the equals (=) from the command line and treats the left and right side of the equals as separate arguments for the batch file. Thus, the arguments to the java executable for an argument like (for example) --profiles=log will be split in two arguments as --profiles and log. To avoid this you will have to enclose the entire argument between quotes (") as in "--profiles=log".

  • No labels