ops4j / org.ops4j.pax.web

OSGi R7 Http Service, Whiteboard and Web Applications (OSGi CMPN Release chapters 102, 140 and 128) implementation using Jetty 9, Tomcat 9 or Undertow 2.

OPS4j Pax Web

What is Pax Web

• OSGi R7 Http Service Specification implementation (OSGi CMPN R7, chapter 102)
• OSGi R7 Web Applications Specification implementation (OSGi CMPN R7, chapter 128)
• OSGi R7 Http Whiteboard Specification implementation (OSGi CMPN R7, chapter 140)

Pax Web extends OSGi Http Service with better servlet support, filters, listeners, error pages and JSPs and some others in order to meet the latest versions of Servlet specs. Pax Web facilitates an easy installation of WAR bundles as well as discovery of web elements published as OSGi services. All of this beside the, standard, programmatic registration as detailed in the HTTP Service specs.

There are 3 equivalent (in terms of functionality) implementations in Pax Web:

• pax-web-jetty bundle uses Jetty 9.4.x
• pax-web-tomcat bundle uses Tomcat 9.0.x
• pax-web-undertow bundle uses Undertow 2.2.x

Documentation

• https://ops4j1.jira.com/wiki/spaces/paxweb/overview or alternative (work in progress)
• http://ops4j.github.io/pax/web/index.html

Contributing

In OPS4J, everyone is invited to contribute. We don't require any paperwork or community reputation. All we ask you is to move carefully and to clean up after yourself:

• Describe your problem or enhancement request before submitting a solution.
• Submit a GitHub issue before creating a pull request. This is required for the release notes.
• For discussions, the mailing list is more suitable than GH issues.
• Any bugfix or new feature must be covered by regression tests.

Building Pax Web

mvn clean install

NB: if you want to avoid test execution: mvn clean install -DskipTests

Releasing Pax Web

mvn -Prelease -Darguments="-Prelease" release:prepare -DautoVersionSubmodules=true

mvn -Prelease -Darguments="-Prelease" -Dgoals=deploy release:perform

Go to oss.sonatype.org and push pax-web to central.

If you want more information about releasing, please take a look on:

https://ops4j1.jira.com/wiki/spaces/ops4j/pages/12060688/Releasing

org.ops4j.pax.web's Issues

Add integration testing [PAXWEB-6]

Alin Dreghiciu created PAXWEB-6

Add integration testing via spring-osgi IT support or something similar.

---

Fixed in: 0.3.0
Votes: 0, Watches: 0

Ignore slashes in the middle of a URL [PAXWEB-41]

David Leangen created PAXWEB-41

As discussed somewhat in http://issues.ops4j.org/jira/browse/PAXWEB-31, a URL should ignore extra slashes in the middle of a URL.

In other words, the following URLs should both resolve to the same resource:

http://host/path/to/resource
http://host/////path///////to///////resource

---

Fixed in: 0.2.2
Votes: 0, Watches: 0

java.lang.ClassNotFoundException: org.slf4j.Logger when not using Pax Logger [PAXWEB-51]

Alin Dreghiciu created PAXWEB-51

From Guillaume Nodet:

My previous attempt to build the pax-web trunk was about trying to solve this exception:
java.lang.ClassNotFoundException: org.slf4j.Logger
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged (Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at org.mortbay.log.Slf4jLog.<init>(Slf4jLog.java:51)
at org.mortbay.log.Slf4jLog.getLogger(Slf4jLog.java:138)
at org.mortbay.log.Log.getLogger (Log.java:196)
at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:475)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
at org.mortbay.jetty.handler.HandlerWrapper.doStart (HandlerWrapper.java:117)
at org.mortbay.jetty.Server.doStart(Server.java:210)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
at org.ops4j.pax.web.service.internal.JettyServerImpl.start (JettyServerImpl.java:54)
at org.ops4j.pax.web.service.internal.ServerControllerImpl$Stopped.start(ServerControllerImpl.java:208)
at org.ops4j.pax.web.service.internal.ServerControllerImpl.start(ServerControllerImpl.java :55)
at org.ops4j.pax.web.service.internal.ServerControllerImpl$Started.configure(ServerControllerImpl.java:166)
at org.ops4j.pax.web.service.internal.ServerControllerImpl.configure(ServerControllerImpl.java :78)
at org.ops4j.pax.web.service.internal.HttpServiceConfigurerImpl.configure(HttpServiceConfigurerImpl.java:38)
at org.ops4j.pax.web.service.ConfigAdminConfigurationSynchronizer$ConfigurationTarget.updated (ConfigAdminConfigurationSynchronizer.java:196)
at org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceUpdate.run(ConfigurationManager.java:888)
at org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java :89)

This happens when starting pax-web when pax-logging is already installed.
I'm not sure if the problem is in jetty (I suppose the "at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)" line means that it does not really use the correct classloader, or if pax-web should fix that somehow.

---

Affects: 0.2.0, 0.2.1
Fixed in: 0.2.2
Votes: 0, Watches: 0

Handle content encoding [PAXWEB-7]

Alin Dreghiciu created PAXWEB-7

Automatically set the content encoding if HttpContext returns null from getMimeType.

---

Fixed in: 0.3.0
Votes: 0, Watches: 0

Support https [PAXWEB-27]

Alin Dreghiciu created PAXWEB-27

---

Affects: 0.2.0
Fixed in: 0.2.1
Votes: 0, Watches: 0

Set servlet init params [PAXWEB-19]

Alin Dreghiciu created PAXWEB-19

Use the init params received from registerServlet as init params for the underling jetty servlet.

---

Fixed in: 0.2.0
Votes: 0, Watches: 0

Validate HttpService.registerServlet parameters [PAXWEB-17]

Alin Dreghiciu created PAXWEB-17

Validate httpService register Servlet parameters according to specs

---

Fixed in: 0.2.0
Votes: 0, Watches: 0

Handle concurent registrations and unregistration [PAXWEB-48]

Alin Dreghiciu created PAXWEB-48

Concurrent registrations/unregistrations are not handled by the moment, fact that could lead into problems.

---

Affects: 0.2.0, 0.2.1, 0.2.2
Fixed in: 0.2.3
Votes: 0, Watches: 0

Send HttpServletResponse.SC_NOT_FOUND as response if there is no match [PAXWEB-8]

Alin Dreghiciu created PAXWEB-8

If the http service does not match the request against the registered resources / servlets send back HttpServletResponse.SC_NOT_FOUND. This is specified in the specs.

---

Fixed in: 0.2.0
Votes: 0, Watches: 0

Pax-Web doesn't correctly handle file: URLs for the javax.servlet.context.tempdir property [PAXWEB-52]

Stuart McCulloch created PAXWEB-52

Currently the Pax-Web service treats the javax.servlet.context.tempdir as a plain filename, and passes it straight to the File constructor. However, it appears from the tests that it should also handle file: URLs, as there is a test where a file: URL is passed in. At the moment this creates a local "file:" directory, which is why the test passes, but it should really try to interpret the string as a URI and use that to create the File.

---

Affects: 0.2.1
Fixed in: 0.2.2
Votes: 0, Watches: 0

HttpService HttpServletRequest attributes [PAXWEB-13]

Alin Dreghiciu created PAXWEB-13

Shall we handle in any way the HttpServletReuest attributes AUTHENTICATION_TYPE, AUTHORIZATION, REMOTE_USER specified in 102.11.2 or is the job of the HttpContext implementor? What about DefaultHttpContext?

---

Fixed in: 0.2.0
Votes: 0, Watches: 0

Use released version of pax wicket 0.5.1 [PAXWEB-24]

Alin Dreghiciu created PAXWEB-24

Use the just released version of pax wicket as sample

---

Fixed in: 0.2.0
Votes: 0, Watches: 0

ssl parameters not taking effect [PAXWEB-44]

David Leangen created PAXWEB-44

Despite setting the options:

-Dorg.osgi.pax.web.ssl.password=password
-Dorg.osgi.pax.web.ssl.keypassword=password

I am still getting prompted for a password, which implies that these configurations are not taking effect.

---

Fixed in: 0.2.1
Votes: 0, Watches: 0

Cannot connect to port 8443, even though pax web appears to have started correctly [PAXWEB-45]

David Leangen created PAXWEB-45

As per log message below, pax web appears to have started correctly.

However, I am not able to connect to port 8443 via my browser.

2007-10-02 13:45:19.233::INFO: Logging to STDERR via org.mortbay.log.StdErrLogorg.ops4j.pax.logging.apiorg.ops4j.pax.web.service.SimpleHttpServiceConfiguration : http secure enabled not set. fallback to class org.ops4j.pax.web.service.SysPropsHttpServiceConfiguration
org.ops4j.pax.logging.apiorg.ops4j.pax.web.service.SimpleHttpServiceConfiguration : http secure port not set. fallback to class org.ops4j.pax.web.service.SysPropsHttpServiceConfiguration
org.ops4j.pax.logging.apiorg.ops4j.pax.web.service.SysPropsHttpServiceConfiguration : http secure port not set. fallback to class org.ops4j.pax.web.service.DefaultHttpServiceConfiguration
org.ops4j.pax.logging.apiorg.ops4j.pax.web.service.SimpleHttpServiceConfiguration : ssl keystore not set. fallback to class org.ops4j.pax.web.service.SysPropsHttpServiceConfiguration
org.ops4j.pax.logging.apiorg.ops4j.pax.web.service.SysPropsHttpServiceConfiguration : ssl keystore not set. fallback to class org.ops4j.pax.web.service.DefaultHttpServiceConfiguration
org.ops4j.pax.logging.apiorg.ops4j.pax.web.service.SimpleHttpServiceConfiguration : ssl password not set. fallback to class org.ops4j.pax.web.service.SysPropsHttpServiceConfiguration
org.ops4j.pax.logging.apiorg.ops4j.pax.web.service.SysPropsHttpServiceConfiguration : ssl password not set. fallback to class org.ops4j.pax.web.service.DefaultHttpServiceConfiguration
org.ops4j.pax.logging.apiorg.ops4j.pax.web.service.SimpleHttpServiceConfiguration : ssl keystore password not set. Fallback to class org.ops4j.pax.web.service.SysPropsHttpServiceConfiguration
org.ops4j.pax.logging.apiorg.ops4j.pax.web.service.SysPropsHttpServiceConfiguration : ssl keystore password not set. Fallback to class org.ops4j.pax.web.service.DefaultHttpServiceConfiguration
jetty.ssl.password :
edited by dleangen: user entry replaces text
jetty.ssl.keypassword : edited by dleangen: user entry replaces text
org.ops4j.pax.logging.apiorg.ops4j.pax.web.service.internal.JettyServer : adding connectorSslSocketConnector @ 0.0.0.0:8443
org.ops4j.pax.logging.apiorg.ops4j.pax.web.service.internal.JettyServer : adding context
org.ops4j.pax.logging.apiorg.ops4j.pax.web.service.internal.JettyServer : added context: org.ops4j.pax.web.service.internal.HttpServiceContext@50988 {/,null}

org.ops4j.pax.logging.apiorg.ops4j.pax.web.service.internal.JettyServer : starting org.ops4j.pax.web.service.internal.JettyServerImpl@b4e29b
2007-10-02 13:45:37.358::INFO: jetty-6.1.3
2007-10-02 13:45:37.424::INFO: Started SocketConnectorWrapper @ 0.0.0.0:8080
org.ops4j.pax.logging.apiorg.ops4j.pax.web.service.internal.JettyServer : started org.ops4j.pax.web.service.internal.JettyServerImpl@b4e29b
org.ops4j.pax.logging.apiorg.ops4j.pax.web.service.internal.ServerControllerImpl : started server: org.ops4j.pax.web.service.internal.ServerControllerImpl@c39a20. current state: org.ops4j.pax.web.service.internal.ServerControllerImpl$Started@e66f56
org.ops4j.pax.logging.apiorg.ops4j.pax.web.service.internal.ServerControllerImpl : configuring server: org.ops4j.pax.web.service.internal.ServerControllerImpl@c39a20 -> org.ops4j.pax.web.service.SimpleHttpServiceConfiguration@1bbd23f
org.ops4j.pax.logging.apiorg.ops4j.pax.web.service.internal.ServerControllerImpl : stopping server: org.ops4j.pax.web.service.internal.ServerControllerImpl@c39a20. current state: org.ops4j.pax.web.service.internal.ServerControllerImpl$Started@e66f56
org.ops4j.pax.logging.apiorg.ops4j.pax.web.service.internal.JettyServer : stopping org.ops4j.pax.web.service.internal.JettyServerImpl@b4e29b
2007-10-02 13:45:37.793::INFO: Started SslSocketConnector @ 0.0.0.0:8443
org.ops4j.pax.logging.apiorg.ops4j.pax.web.service.internal.JettyServer : stopped org.ops4j.pax.web.service.internal.JettyServerImpl@b4e29b
org.ops4j.pax.logging.apiorg.ops4j.pax.web.service.internal.ServerControllerImpl : stopped server: org.ops4j.pax.web.service.internal.ServerControllerImpl@c39a20. current state: org.ops4j.pax.web.service.internal.ServerControllerImpl$Stopped@979e8b
org.ops4j.pax.logging.apiorg.ops4j.pax.web.service.internal.ServerControllerImpl : starting server: org.ops4j.pax.web.service.internal.ServerControllerImpl@c39a20. current state: org.ops4j.pax.web.service.internal.ServerControllerImpl$Stopped@979e8b
org.ops4j.pax.logging.apiorg.ops4j.pax.web.service.SimpleHttpServiceConfiguration : http enabled not set. fallback to class org.ops4j.pax.web.service.SysPropsHttpServiceConfiguration
org.ops4j.pax.logging.apiorg.ops4j.pax.web.service.SysPropsHttpServiceConfiguration : http enabled not set. fallback to class org.ops4j.pax.web.service.DefaultHttpServiceConfiguration
org.ops4j.pax.logging.apiorg.ops4j.pax.web.service.SimpleHttpServiceConfiguration : http port not set. fallback to class org.ops4j.pax.web.service.SysPropsHttpServiceConfiguration
org.ops4j.pax.logging.apiorg.ops4j.pax.web.service.internal.JettyServer : adding connectorSocketConnectorWrapper @ 0.0.0.0:8080
org.ops4j.pax.logging.apiorg.ops4j.pax.web.service.SimpleHttpServiceConfiguration : http secure enabled not set. fallback to class org.ops4j.pax.web.service.SysPropsHttpServiceConfiguration
org.ops4j.pax.logging.apiorg.ops4j.pax.web.service.SimpleHttpServiceConfiguration : http secure port not set. fallback to class org.ops4j.pax.web.service.SysPropsHttpServiceConfiguration
org.ops4j.pax.logging.apiorg.ops4j.pax.web.service.SysPropsHttpServiceConfiguration : http secure port not set. fallback to class org.ops4j.pax.web.service.DefaultHttpServiceConfiguration
org.ops4j.pax.logging.apiorg.ops4j.pax.web.service.SimpleHttpServiceConfiguration : ssl keystore not set. fallback to class org.ops4j.pax.web.service.SysPropsHttpServiceConfiguration
org.ops4j.pax.logging.apiorg.ops4j.pax.web.service.SysPropsHttpServiceConfiguration : ssl keystore not set. fallback to class org.ops4j.pax.web.service.DefaultHttpServiceConfiguration
org.ops4j.pax.logging.apiorg.ops4j.pax.web.service.SimpleHttpServiceConfiguration : ssl password not set. fallback to class org.ops4j.pax.web.service.SysPropsHttpServiceConfiguration
org.ops4j.pax.logging.apiorg.ops4j.pax.web.service.SysPropsHttpServiceConfiguration : ssl password not set. fallback to class org.ops4j.pax.web.service.DefaultHttpServiceConfiguration
org.ops4j.pax.logging.apiorg.ops4j.pax.web.service.SimpleHttpServiceConfiguration : ssl keystore password not set. Fallback to class org.ops4j.pax.web.service.SysPropsHttpServiceConfiguration
org.ops4j.pax.logging.apiorg.ops4j.pax.web.service.SysPropsHttpServiceConfiguration : ssl keystore password not set. Fallback to class org.ops4j.pax.web.service.DefaultHttpServiceConfiguration
jetty.ssl.password : org.ops4j.pax.logging.api

---

Affects: 0.2.0
Fixed in: 0.2.1
Votes: 0, Watches: 0

Documentation [PAXWEB-1]

Alin Dreghiciu created PAXWEB-1

Write documentation.
There is not to much to write about the functionality since it can be read from the compendium but it should contain:

• how to install and run (via pax runner)
• what to include as dependencies in maven
• how to configure with different configuration options (system properties, configuration admin)
• what is the priority of configuration options (fist config admin, then fall back to system props)

---

Fixed in: 0.2.2
Votes: 1, Watches: 1

Simplify the maven build structure of Pax Web [PAXWEB-40]

Alin Dreghiciu created PAXWEB-40

Symplify the maven build structure as Pax Web does not need a submodule structure. There is pretty sure that there will not be another module beside the service in Pax Web.

---

Affects: 0.2.0
Fixed in: 0.2.1
Votes: 0, Watches: 0

Use released version of pax runner 0.3.2 [PAXWEB-23]

Alin Dreghiciu created PAXWEB-23

Use the just released version of pax runner 0.3.2 instead on the snapshot one.

---

Fixed in: 0.2.0
Votes: 0, Watches: 0

Use Peter's Kriens fileinstall to configure via Config admin [PAXWEB-4]

Alin Dreghiciu created PAXWEB-4

Add a new imported project via pax construct to use fileinstall.
This utility can act as a management agent for Configuration Admin and will be used to scan a folder for properties files, properties that are automatically configured via config admin for http service.
Document how to do that.

---

Fixed in: 0.2.0
Votes: 0, Watches: 0

Automatically unregister resources/servlets in case of a bundle that unbinds from http service [PAXWEB-5]

Alin Dreghiciu created PAXWEB-5

In case that a bundle unbinds from http service the resources / servlets registered by that bundle should automatically be unregistered.

---

Fixed in: 0.2.0
Votes: 0, Watches: 0

OSGi TCK test failure: Verification of authentication under handleSecurity() [PAXWEB-54]

Stuart McCulloch created PAXWEB-54

expects: Remote User is unknown user, Authentication Type is Basic

but gets: Remote User is null, Authentication Type is null

---

Affects: 0.2.1
Fixed in: 0.2.2
Votes: 0, Watches: 0

Do not allow duplicate servlet registration within the whole service [PAXWEB-11]

Alin Dreghiciu created PAXWEB-11

Throw ServletException in case that the requested servlet registration is already in use withing all registered servlets regardless the bundle that made the registration.
This is a mandatory specs requirement: 102.11.3.3.

---

Fixed in: 0.2.0
Votes: 0, Watches: 0

Move samples / demo to a subfolder = samples [PAXWEB-26]

Alin Dreghiciu created PAXWEB-26

Move the existing samples (demo, demo.minimal, configurer.simple) to a subfolder = samples to have a clean folder structure

---

Fixed in: 0.2.0
Votes: 0, Watches: 0

Embed jetty jars into the service jar [PAXWEB-25]

Alin Dreghiciu created PAXWEB-25

Embed jetty jars into the service to ease the deployment of pax web.
Also embed servlet 2.5 from jetty and export it.

---

Fixed in: 0.2.0
Votes: 0, Watches: 0

handle the case that the configured port is in use [PAXWEB-9]

Alin Dreghiciu created PAXWEB-9

handle the case that by starting the server the configured ports are in use.
What shall be done?

• just log and do not start the server but keep the http service up? unregister the service?

---

Affects: 0.2.0
Fixed in: 0.2.1
Votes: 0, Watches: 1

Change symbolic name to org.ops4j.pax.web.service [PAXWEB-39]

Alin Dreghiciu created PAXWEB-39

Change bundle symbolic name to org.ops4j.pax.web.service.

---

Affects: 0.2.0, 0.2.1
Fixed in: 0.2.2
Votes: 0, Watches: 0

Support configuration via configuration admin [PAXWEB-2]

Alin Dreghiciu created PAXWEB-2

The http service should be configurable via config admin if present.

---

Fixed in: 0.2.0
Votes: 0, Watches: 0

SocketTimeoutException: Read timed out [PAXWEB-20]

Toni Menzel created PAXWEB-20

Just encountered the following leak in paxweb:
530016 btpool0-2 DEBUG org.mortbay.log - EXCEPTION
java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at org.mortbay.io.ByteArrayBuffer.readFrom(ByteArrayBuffer.java:168)
at org.mortbay.io.bio.StreamEndPoint.fill(StreamEndPoint.java:99)
at org.mortbay.jetty.bio.SocketConnector$Connection.fill(SocketConnector.java:196)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:281)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:202)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:378)
at org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:226)
at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442)
530019 btpool0-2 DEBUG org.mortbay.log - EOF

the exception occures if i just register a static resource (say html file) and (successfully) request it in a browser.
The problem is reproducable. I will have a look at it later today but maybe someone already solved that..:wink:

Toni

---

Fixed in: 0.2.0
Votes: 0, Watches: 0

Enable optional usage of logging [PAXWEB-28]

Alin Dreghiciu created PAXWEB-28

Remove the "hard" dependency on logging and make it optional.

---

Affects: 0.2.0
Fixed in: 0.2.2
Votes: 0, Watches: 0

support adding HttpSessionListeners and setting session timeouts [PAXWEB-50]

matthew hawthorne created PAXWEB-50

In order to upgrade Jetty, I attempted to use the "org.ops4j.pax.web.pax.web.service" bundle to replace our existing "org.ungoverned.osgi.bundle.http" bundle, which runs with an embedded Jetty4.

In our Jetty4 environment, we were able to use reflection on the SessionContext to get a Jetty ServletHandler, which allowed us to add and remove HttpSessionListners, as well as set the session timeout value.

However, using the Pax Web bundle I was unable to find a clear path to do this. The provided to me in the SessionContext is of type org.ops4j.pax.web.service.internal.HttpServiceContext$SContext, which extends org.mortbay.jetty.servlet.Context$SContext. The parent class of the latter has the getServletHandler() method, but I can't get it reflectively since I am passed an inner class.

I'm unsure whether there is anything that can be done about this in Pax Web, or if I need to push the Jetty developers to provide better programmatic access to configure things that are typically found in web.xml.

Your feedback and ideas on this would be appreciated.

---

Affects: 0.2.1
Fixed in: 0.2.2
Votes: 0, Watches: 2

Implement HttpService.unregister() [PAXWEB-15]

Alin Dreghiciu created PAXWEB-15

Implement http service unregister according to compendium specs 102.11.3.4

---

Fixed in: 0.2.0
Votes: 0, Watches: 0

Add parameter for ssl port configuration [PAXWEB-42]

David Leangen created PAXWEB-42

Add parameter:

org.ops4j.pax.web.ssl.port

So that the ssl port can be configured.

---

Fixed in: 0.2.1
Votes: 0, Watches: 0

Isolate servlet context per http contexts used in registration [PAXWEB-21]

Alin Dreghiciu created PAXWEB-21

This task is a presumption based on specs requirement: 102.11.3.3: the servlets registered with the same http context must share the same servlet context. The presumption is that the shared servlet context is only shared by those servlets that share the same http context.
This implies that the attributes stored in servlet context are isolated per http context.

---

Affects: 0.2.0, 0.2.1
Fixed in: 0.2.2
Votes: 0, Watches: 0

---

Referenced issues

aggregation of:

• #367 - OSGi TCK test failure: Verification of ServletContext sharing [PAXWEB-55]

Add JavaDoc [PAXWEB-29]

Alin Dreghiciu created PAXWEB-29

Document code using JavaDoc.

---

Fixed in: 0.2.2
Votes: 0, Watches: 0

Default keystore not correct [PAXWEB-46]

David Leangen created PAXWEB-46

Default keystore should be $ {user.home}

/.keystore.

However, I get the following error:

java.io.FileNotFoundException: /home/dleangen.keystore (No such file or directory)

Note: missing "/"

---

Fixed in: 0.2.2
Votes: 0, Watches: 0

Cleanup various OSGi imports+exports to run Pax-Web under the OSGi TCK [PAXWEB-53]

Stuart McCulloch created PAXWEB-53

General task to get Pax-Web working under the OSGi TCK test harness, without requiring Pax-Logging

---

Affects: 0.2.1
Fixed in: 0.2.2
Votes: 0, Watches: 0

Addapt build process to latest changes from pax-construct-0.1.6 [PAXWEB-22]

Alin Dreghiciu created PAXWEB-22

As with pax construct 0.1.6 there are some small changes to the generated the pom.xml as:
1. project (root project) groups should be org.ops4j.pax (not org.ops4j.pax.web
2. "compiled bundles" as service will have a group org.ops4j.pax.web.bundles
3. add entry <relativePath> to <parent>

---

Fixed in: 0.2.0
Votes: 0, Watches: 0

Disable prompt when ssl password not set [PAXWEB-43]

David Leangen created PAXWEB-43

If https is enabled (by setting org.osgi.service.http.secure.enabled to "true"), and if no password is set in either org.ops4j.pax.web.ssl.password or org.ops4j.pax.web.ssl.keypassword, then the bundle halts and waits for command-line input from the user.

This halts bundle startup, which completely messes up platform startup.

In this situation, https should be disabled, with an error logged.

---

Fixed in: 0.2.2
Votes: 0, Watches: 0

Change name of the service bundle to Pax Web [PAXWEB-38]

Alin Dreghiciu created PAXWEB-38

Change the current name: service org.ops4j.pax.web.service to a frendlier one: Pax Web

---

Affects: 0.2.0
Fixed in: 0.2.1
Votes: 0, Watches: 0

Move pax web samples to the same level as the other projects (same level as pax web) [PAXWEB-30]

Alin Dreghiciu created PAXWEB-30

By having the samples in pax web folder the build time is quite hihg as all the samples are also built. The samples contains pax construct based imports that when build will expand the dependencies resulting in high built time. To not build them and start the build separately will interfeer with releasing and ci.

---

Fixed in: 0.2.0
Votes: 0, Watches: 0

Servlets registered with the same HttpContext must share the same ServletContext [PAXWEB-12]

Alin Dreghiciu created PAXWEB-12

Servlets registered with the same HttpContext must share the same ServletContext.
This is a mandatory specs requirement: 102.11.3.3.

---

Fixed in: 0.2.0
Votes: 0, Watches: 0

Servlets can not be registered again under the same alias after unregistration [PAXWEB-35]

Alin Dreghiciu created PAXWEB-35

It seems like if:

1. register a servlet
   2. unregister the servlet
   3. register the servlet again with the same alias

the step 3 will crash with an exception pointing out that the alias is already in use, which is not the case.

This could be exemplified by using the pax-samples extender.whiteboard and then stopping the extender.whitboard bundle and starting it again.

---

Affects: 0.2.0
Fixed in: 0.2.1
Votes: 0, Watches: 0

Implement resources handling [PAXWEB-14]

Alin Dreghiciu created PAXWEB-14

Implement http service handling of resources according to compendium specs.

---

Fixed in: 0.2.0
Votes: 0, Watches: 0

Support extra jetty configuration options [PAXWEB-3]

Alin Dreghiciu created PAXWEB-3

The service should support extra configuration options that are available from jetty which are useful for tunning jetty.

---

Fixed in: 0.3.0
Votes: 0, Watches: 0

Servlet spec requires an ServletContext attribute named "javax.servlet.context.tempdir" [PAXWEB-49]

NiclasH created PAXWEB-49

We need to start looking into the Servlet spec and ensure that these kinds of things are supported.

---

Fixed in: 0.3.0
Votes: 0, Watches: 0

Validate HttpService.registerResources parameters [PAXWEB-16]

Alin Dreghiciu created PAXWEB-16

Validate httpService register Resources according to specs

---

Fixed in: 0.2.0
Votes: 0, Watches: 0

Add toString() for better logging [PAXWEB-47]

Alin Dreghiciu created PAXWEB-47

For those classes that get logged will be usefull to add toString(0 implementation so nicer logging messages will be displayed.

---

Affects: 0.2.0
Fixed in: 0.2.1
Votes: 0, Watches: 0

OSGi TCK test failure: Verification of ServletContext sharing [PAXWEB-55]

Stuart McCulloch created PAXWEB-55

expects: Parameter param1 has value: null

but gets: Parameter param1 has value: val1

---

Affects: 0.2.1
Fixed in: 0.2.2
Votes: 0, Watches: 0

---

Referenced issues

is aggregated into:

• #332 - Isolate servlet context per http contexts used in registration [PAXWEB-21]

Do not allow duplicate alias registration within the whole service [PAXWEB-10]

Alin Dreghiciu created PAXWEB-10

Throw NamespaceException in case that the requested alias registration is already in use withing all registered resources / requests regardless the bundle that made the registration.
This is a mandatory specs requirement: 102.4, 102.11.4 .

---

Fixed in: 0.2.0
Votes: 0, Watches: 0

Honor org.osgi.service.http.port property [PAXWEB-18]

Toni Menzel created PAXWEB-18

it turns out that paxweb always uses port 80 for http which prevents it from working on almost every unix based system.

looks like SysPropsHttpServiceConfiguration is going to be the responsible class.. but not currently.
Instead it asks for the OS-Properties.

as of compendium 102.9 it should look for OSGI-Env. properties.

if its ok I can do it.. ??
everyone?

---

Fixed in: 0.2.0
Votes: 0, Watches: 1

support trimming of double trailing // [PAXWEB-31]

PeterN created PAXWEB-31

in certain cases with Wicket, I am getting URLs like http://localhost:8080/test// which leads to PaxWeb not finding the context, but http://localhost:8080/test/ and http://localhost:8080/test//hi.html seem to work fine.

Is this a bug in my app&wicket or would it be possible to just trim trailing slashes?

---

Fixed in: 0.2.1
Votes: 1, Watches: 1