Hi,
The problem here is, that the JcrResolverFactoryImpl is trying to bind
ServletResourceProvider instances which causes NPEs because the
component is not activated yet.
Am Montag, den 28.01.2008, 09:10 +0100 schrieb Bertrand Delacretaz:
> On Jan 28, 2008 12:13 AM, Felix Meschberger <[EMAIL PROTECTED]> wrote:
>
> > ...The main question is, whether the ServletResolver bundle is launched
> > before or after the bundle containing your servlet....
>
> Could we make use of OSGi's run levels to better control this?
> Assuming bundles with a lower run levels are always started first, but
> I don't know if that's specified.
That would be one solution, yet it would not be very stable as you
cannot force all users to correctly set start levels. To me start levels
are an instrument for the system administration to be able to control
which services are started or not, just like the run levels in a *nix
system.
If we use start levels to handle dependencies, we have IMHO a problem.
>
> I'm not sure how we can specify this level when creating bundles, but
> if it's easy we could define some standard run levels, i.e. 10 for
> Sling infrasctructure, 20 for services like WebDAV, 30 for user code,
> etc.
This would make sense from an administrative point of view, and in fact
was the intent initially but was lost over time. We might want to
reintroduce this with specific setup in Launchpad, e.g. by defining
multitple bundle resource folders.
Today we have .../resources/corebundles and .../resources/bundles. To
support start levels we might have .../resources/bundles${level} where
${level} would be the startlevel to be used for the bundles contained.
So we would have:
.../resources/bundles1 - start level 1 bundles such as logging,
sling console and
OSGi services
.../resources/bundles10 - for Sling infrastructure
.../resources/bundles20 - for extended services like WebDAV
.../resources/bundles30 - for user code
WDYT ?
Regards
Felix
