That sounds reasonable... there's no need to block the http service or
servlets with their own HttpContexts from starting up, even when
waitForCustomContext=true.
Thanks,
Josh
On Thu, Mar 11, 2010 at 2:27 AM, Alin Dreghiciu wrote:
> Hi,
>
> No there is no such option. Even if we would implement
Hi,
No there is no such option. Even if we would implement a lookup for a
default http context factory without a special handling we can still run
into ordering problems which I do not like.
So, to avoid such situation (ordering) I would propose a solution like: when
there is a need for a default
I've been reading through the mail archives and the ops4j Jira, but I can't
seem to figure out whether there is support for registering a custom default
http context (via whiteboard or otherwise).
My use case is this: I use a 3rd party bundle (Apache CXF), which registers
servlets using a null Htt
