Whiteboard Implementation does not handle R6 resource registration patterns

Description

The current whiteboard implementation does not handle service registrations for resource definitions correctly. According to Enterprise R6 Specification 140.6 (Registering Resources) the service property "osgi.http.whiteboard.resource.pattern" allows to define certain patterns:

  • "/path/*" – for path mapping,

  • "*. – for extension mapping,

  • "" – for context root,

  • "/" – for default servlet,

  • any other string – for exact mapping.

Registering a mapping to a folder, e.g. /www, inside of the bundle that holds resources should use the first pattern, e.g. "/assets/*". But the current implementation requires to use "/assets" as pattern.

Environment

None

Activity

Show:
Achim Nierbeck
November 28, 2017, 9:45 PM

cause of this, the resource pattern is currently used as the alias name mapping.

Grzegorz Grzybek
November 28, 2017, 9:53 PM

alias and name params are a bit confusing... with I did some changes, maybe I broke something?

Achim Nierbeck
November 28, 2017, 10:21 PM

... I doubt that, this ticket is older then PAXWEB-1114, but I agree, alias and name are confusing.
It worked with the initial Whiteboard extending mechanism for Pax Web, but since we now have a OSGi std. for the Whiteboard extender, the old world, doesn't really work as well.

Grzegorz Grzybek
June 25, 2018, 10:52 AM

Fixed here in pax-web-6.0.x branch
Fixed here in pax-web-6.1.x branch
Fixed here in pax-web-7.0.x branch
Fixed here in pax-web-7.1.x branch
Fixed here in master branch

Assignee

Grzegorz Grzybek

Reporter

Peter Schyma

Labels

None

Components

Fix versions

Affects versions

Priority

Major
Configure