Failure using ResourceMapping via Blueprint

Description

Hi guys, apologies for the delay in filing this, life has been chaotic recently. I've spent the last couple of days working through this issue with ResourceMapping in 3.0.0.M3. As it turns out, the ResourceServlet is getting configured and added properly, but the context that it is added to is never started.

The Blueprint configuration I am using and which works in Pax Web 2.1.0 is the following:

When a request is made for a resource that has been added in this manner, the call chain makes it's way to org.eclipse.jetty.server.handler.ContextHandler#checkContext, which starts by looking at _availability. In my case, this is always set to __STOPPED. No error is generated on the console and a "Not found" screen is returned. One would presume from this that the context is not started yet, but it's not clear who or what starts it since I'm not familiar enough (yet) to find what changed.

More as I get it!

Environment

None

Activity

Show:
Achim Nierbeck
March 13, 2013, 10:51 PM

Some more input on this would be nice
Or better a simple itest for verification.
What else is registered in this context?

Achim Nierbeck
March 15, 2013, 2:45 PM

Wasn't able to reproduce this, a new test to the WhiteboardIntegrationTest has been added.

Branch: refs/heads/master
Home: https://github.com/ops4j/org.ops4j.pax.web
Commit: 6ce26f5e6a9deca871f8e5a898e55bc625563ffe
https://github.com/ops4j/org.ops4j.pax.web/commit/6ce26f5e6a9deca871f8e5a898e55bc625563ffe
Date: 2013-03-15 (Fri, 15 Mar 2013)

Changed paths:
M itest/src/test/java/org/ops4j/pax/web/itest/WhiteboardIntegrationTest.java

Assignee

Achim Nierbeck

Reporter

BrianB

Labels

None

Fix versions

Affects versions

Priority

Major
Configure