Right, using url handlers could lead to such problems if the url handlers are not registered yet. I guess a possible solution would be to change the karaf configuration so that url handlers are installed and started very early. This can be done by modifying the etc/startup.properties or modifying the start level of the bundles for your url handlers once they installed.
On Wed, Apr 28, 2010 at 09:46, Bengt Rodehav <[email protected]> wrote: > I have a problem with the startup ordering in Karaf. My explicit > problem is that I use iPOJO's Online Manipulator which gives me the > possibility to deploy iPOJO components using the "ipojo:" protocol. > However, it seems impossible to get an automatic installation to work > using Karaf features this way. > > I need to have the iPOJO Online Manipulator started (not just > resolved) before I even try to resolve my iPOJO components since I > refer to them using the "ipojo:" protocol. How can I solve this? I was > hoping that it was possible to specify a startlevel for a specific > feature (in the org.apache.felix.karaf.features.cfg) so that it is > guaranteed to start after other required features. > > I have the same problem when deploying a war. In that case I must be > sure that the "pax-url-war" feature is started first. > > This must be a common problem and I'm hoping there is a standard > recommended way to handle this. > > I'm using Karaf 1.4.0 and iPOJO 1.4.0. > > /Bengt > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
