System Requirements- Java5 virtual machine running on a supported operating system.
- An OSGi framework compliant with the R4 Core specification.
- Pax Logging Service.
- (Optional) A Config Admin Service that is R4 compliant. (see configuration section for details)
InstallationManual installation- Add the following dependency to your pax runner pom:
Code Block |
---|
<dependency>
<groupId>org.ops4j.pax.web</groupId>
<artifactId>pax-web-service</artifactId>
<version>0.2.1</version>
</dependency>
|
- Ensure that you have the following repository:
Code Block |
---|
<repository>
<id>ops4j.repository</id>
<url>http://repository.ops4j.org/maven2</url>
</repository>
|
- Start pax runner
- ! you must have a logging framework installed
- Create a project using
pax-create-project (if you do not already have one) - Ensure that you have the following repository:
Code Block |
---|
<repository>
<id>ops4j.repository</id>
<url>http://repository.ops4j.org/maven2</url>
</repository>
|
- Import pax web bundle using
pax-import-bundle -g org.ops4j.pax.web -a pax-web-service -v 0.2.1 - Start
pax-provision - ! you must have a logging framework installed
BuildingThe source code can be build using Maven 2 ( >= 2.0.6, not tested for maven < 2.0.6 ) Building the service- Checkout the source code
- Go to the root of the downloaded project and run the following:
Code Block |
---|
mvn clean install
|
Building the samples- Checkout the source code
- Go to the root of the downloaded project and run the following:
Code Block |
---|
mvn clean install
|
Source code Anchor |
---|
| SourceCodeService |
---|
| SourceCodeService |
---|
|
Service source codeYou can download the source code from: https://scm.ops4j.org/repos/ops4j/projects/pax/web You can browse the source code using FishEye at http://scm.ops4j.org/browse/OPS4J/projects/pax/web. Anchor |
---|
| SourceCodeSamples |
---|
| SourceCodeSamples |
---|
|
Samples source codeYou can download the source code from: https://scm.ops4j.org/repos/ops4j/projects/pax/web-samples You can browse the source code using FishEye at http://scm.ops4j.org/browse/OPS4J/projects/pax/web-samples. Issue trackerThe issue tracker is to be found at http://issues.ops4j.org/jira/browse/PAXWEB. Here are the current open issues: Jira Issues |
---|
columns | summary |
---|
url | http://issues.ops4j.org/jira/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?&pid=10110&status=1&sorter/field=issuekey&sorter/order=DESC&tempMax=1000 |
---|
|
ConfigurationPax Web supports different configuration options as follows. The default configuration setup will first look for configuration admin, then for environment properties and last for default values. Note that this sequesnce is followed for each configuration property. Anchor |
---|
| configViaProperties |
---|
| configViaProperties |
---|
|
Configuration via OSGi environment propertiesIn order to configure Pax Web via OSGi environment properties set the following properties: Option key | Description | Since |
---|
org.osgi.service.http.port | This property specifies the port used for servlets and resources accessible via HTTP. Default value for this property is 8080. | 0.2.0 | org.osgi.service.http.port.secure | This property specifies the port used for servlets and resources accessible via HTTPS. Default value for this property is 8443. | 0.2.0 | org.osgi.service.http.enabled | This property specifies if the HTTP is enabled. Default value is "true". | 0.2.0 | org.osgi.service.http.secure.enabled | This property specifies if the HTTPS is enabled. Default value is "false". | 0.2.0 | org.ops4j.pax.web.ssl.keystore | Path to the keystore file. See Pax Web SSL Configuration for details. | 0.2.1 | org.ops4j.pax.web.ssl.password | Password used for keystore integrity check. See Pax Web SSL Configuration for details. | 0.2.1 | org.ops4j.pax.web.ssl.keypassword | Password used for keystore. See Pax Web SSL Configuration for details. | 0.2.1 | javax.servlet.context.tempdir | A temporary directory that can be accessed via the servlet context attribute with the same name. If not set a default temporary directory wil be used. | 0.3.0 |
Anchor |
---|
| confiViaConfigAdmin |
---|
| confiViaConfigAdmin |
---|
|
Configuration via OSGi Configuration Admin ServicePax Web can be configued via Configuration Admin Service (if available) and it supports all properties from above The PID used for configuration is "org.osgi.service.http.HttpService ". TODO Change LogCheck out the following page to find out what is changed in each version of Pax Web. ExamplesDepartment StoreThe Pax Wicket Department Store example running using Pax Web TODO - explain how to run it. The example exposes a configuration page that can be used to configure Pax Web via the HttpServiceConfigurer. TODO - explain how to run it. Using Configuration Admin from Felix and FileInstall from Peter KriensThis example deploys a configuration admin service and fileinstall for controlling the configuration of Pax Web. Using fileinstall you will be able to change a configuration file (properties file) and see the web server reconfiguring itself. TODO - explain how to run it. ExtensionsPax Web Extender - Insert excerpt |
---|
| paxweb:Pax Web Extender |
---|
| paxweb:Pax Web Extender |
---|
nopanel | true |
---|
|
|