org.springframework.osgi.extender not active

amy

.apache.commons.logging_1.1.1
as you can see the extender is only RESOLVED

The error trying to start it:Code:
osgigt; start 846
getService[System Bundle [0]]({org.eclipse.osgi.framework.console.CommandProvider}={service.ranking=2147483647, service.pid=0.org.eclipse.core.runtime.internal.adaptor.EclipseCommandProvider, service.vendor=Eclipse.org, service.id=19})
getService[System Bundle [0]]({org.eclipse.osgi.framework.console.CommandProvider}={service.ranking=2147483647, service.id=2})
Bundle: Active sl = 6; Bundle 846 sl = 4
dispatchBundleEvent[System Bundle [0]](org.eclipse.osgi.framework.internal.core.FrameworkCommandProvider@4a5ab2)
Starting org..osgi.extender
java.lang.NullPointerException ......................
.........................................
org.osgi.framework.BundleException: The activator org..osgi.extender.internal.activator.ContextLoaderListener for bundle org..osgi.extender is invalid
at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadBundleActivator(AbstractBundle.java:146)
...............................
For the following error I have only discover some posts blaming the log libraries. I try to use slf4j-simple and log4j with switching off the commons-logging from run configuration, but with no luck.

So any opinions, what I have done wrong or missing here is welcome.

Best regards,
Ivan B.

I know it seems pretty lame, but everything seems to be just fine and the  error didn't give me enough information what went wrong... so instead of reverting to older versions i prefer to understand what is really going on even if it will bring shame on me  and my experience as developer  ...

Hi Ivan,
this is a thing i run into some times. The thing which helps me usually is copying and editing the file config.ini as described here: 2008/06...spring-dm.html.
The funny thing with my eclipse installation is that after copying and editing the ini and once trying to start the app with the local ini I have to manually switch back to the generated ini and then it works. Reproducable...
Regards,
dagmar

Portal, I've seen this problems as well but usually only when using equinox from the command line. I've never encountered them during the integration tests when the OSGi platform is used directly, w/o any 'management' tool on top.
The problem usually boils down to the way the bundles are installed and the cache used by the OSGi platform.
My recommendation is to start with a clean plate, with osgi.clean option (i.e. erase the case every time) and with the latest build of equinox. 3.4.2 or 3.5.0 should be good enough.
Also, upgrading Spring DM would be a good idea.