OK, I've just checked with the latest master. IMHO this should work. The problem seams to be the order. You can easily check this that you try to start the bundle 25 AFTER 26 is active. The easiest fix for this problem should be to reorder your bundles in the provision/pom.xml. If you have some time feel free to ping me in the ops4j IRC channel. I think this might be faster and more efficient than by mail :-)
Kind regards, Andreas On Tue, Aug 9, 2011 at 09:08, Rainer W <[email protected]> wrote: > Jup,sorry. mvn pax:provision > > ss: > > Framework is launched. > > id State Bundle > 0 ACTIVE org.eclipse.osgi_3.6.2.R36x_v20110210 > 1 ACTIVE org.springframework.osgi.extender_1.2.1 > 2 ACTIVE org.springframework.osgi.core_1.2.1 > 3 ACTIVE org.springframework.osgi.io_1.2.1 > 4 ACTIVE com.springsource.slf4j.org.apache.commons.logging_1.5.0 > 5 ACTIVE com.springsource.slf4j.api_1.5.0 > Fragments=6 > 6 RESOLVED com.springsource.slf4j.log4j_1.5.0 > Master=5 > 7 ACTIVE org.springframework.aop_2.5.6.SEC01 > 8 ACTIVE org.springframework.beans_2.5.6.SEC01 > 9 ACTIVE org.springframework.context_2.5.6.SEC01 > 10 ACTIVE org.springframework.core_2.5.6.SEC01 > 11 ACTIVE org.springframework.test_2.5.6.SEC01 > 12 ACTIVE com.springsource.org.aopalliance_1.0.0 > 13 ACTIVE com.springsource.edu.emory.mathcs.backport_3.1.0 > 14 ACTIVE com.springsource.org.apache.log4j_1.2.15 > 15 ACTIVE com.springsource.org.apache.commons.logging_1.1.1 > 16 ACTIVE com.springsource.javax.el_2.1.0 > 17 ACTIVE com.springsource.com.sun.enterprise.loader_1.0.0 > 18 ACTIVE com.springsource.javax.activation_1.1.0 > 19 ACTIVE com.springsource.javax.persistence_1.0.0 > 20 ACTIVE com.springsource.javax.portlet_1.0.0 > 21 ACTIVE com.springsource.javax.servlet_2.4.0 > 22 INSTALLED com.springsource.javax.servlet.jsp_2.1.0 > 23 ACTIVE com.springsource.javax.jms_1.1.0 > 24 ACTIVE com.springsource.javax.transaction_1.1.0 > 25 INSTALLED de.bitnoise.demo.pax-wicket-demo-web_1.0.0.SNAPSHOT > 26 ACTIVE org.ops4j.pax.wicket.service_0.8.0.SNAPSHOT > 27 ACTIVE > org.apache.geronimo.specs.geronimo-servlet_2.5_spec_1.2.0 > 28 ACTIVE org.apache.servicemix.bundles.cglib_2.2.0.2 > 29 ACTIVE org.apache.felix.configadmin_1.2.4 > 30 ACTIVE org.ops4j.pax.logging.pax-logging-api_1.4.0 > 31 ACTIVE org.ops4j.pax.logging.pax-logging-service_1.4.0 > 32 ACTIVE org.ops4j.pax.web.pax-web-jetty-bundle_0.7.2 > 33 ACTIVE org.apache.felix.webconsole_3.0.0 > 34 ACTIVE org.apache.felix.webconsole.plugins.event_1.0.2 > 35 ACTIVE > org.apache.felix.org.apache.felix.webconsole.plugins.memoryusage_1.0.0 > > Cheers Rainer > > > On Tue, Aug 9, 2011 at 8:53 AM, Andreas Pieber <[email protected]> wrote: > >> how do you start pw? Pax-Runner/Pax-Construct? Can you do a "bundles" in >> this case. Please use "la" if your on karaf or "lb" on equinox. Either >> you'vent installed all required bundles or (what I expect) they start in the >> wrong order. The pain with spring namespace handlers is that the bundle >> providing the namespace needed to be started before the bundle using it. >> >> Kind regards, >> Andreas >> >> >> On Tue, Aug 9, 2011 at 08:44, Rainer W <[email protected]> wrote: >> >>> 1) I switched to 0.8.0-SNAPSHOT from yesterday evening. >>> 2) attached is the spring xml >>> >>> Cheers Rainer >>> >>> >>> On Tue, Aug 9, 2011 at 4:07 AM, Andreas Pieber <[email protected]>wrote: >>> >>>> Hey Rainer, >>>> >>>> 1) "traces use PW 0.8.0-SNAPSHOT"? >>>> >>>> Do you use PW 0.8 for your experiments or still 0.7.2? >>>> >>>> In case of 0.8 which bundles do you deploy into your osgi environment? >>>> >>>> 2) Can you attach the spring.xml of your bundle? >>>> >>>> You can't import the internal package because it is not exported. What >>>> I'm confused about is that he tries at all. This should not happen since >>>> spring loads the namespace from the bundle classloader of the pw bundle? >>>> >>>> Thanks and kind regards, >>>> Andreas >>>> >>>> On Tue, Aug 9, 2011 at 00:43, Rainer W <[email protected]> wrote: >>>> >>>>> Okay thx, Now, how to get the wicket namespace working? >>>>> >>>>> Spring wants a Namespace handler: >>>>> >>>>> [SpringOsgiExtenderThread-1] DEBUG >>>>> org.springframework.osgi.context.support.OsgiBundleXmlApplicationContext - >>>>> Pre refres >>>>> h error >>>>> org.springframework.beans.factory.parsing.BeanDefinitionParsingException: >>>>> Configuration problem: Unable to locate Spring >>>>> NamespaceHandler for XML schema namespace [ >>>>> http://www.ops4j.org/schema/wicket] >>>>> Offending resource: URL >>>>> [bundleentry://25.fwk1228283922/META-INF/spring/application.xml] >>>>> >>>>> at >>>>> org.springframework.beans.factory.parsing.FailFastProblemReporter.error(FailFastProblemReporter.java:68) >>>>> at >>>>> org.springframework.beans.factory.parsing.ReaderContext.error(ReaderContext.java:85) >>>>> at >>>>> org.springframework.beans.factory.parsing.ReaderContext.error(ReaderContext.java:80) >>>>> at >>>>> org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.error(BeanDefinitionParserDelegate.java:28 >>>>> 1) >>>>> at >>>>> org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDel >>>>> egate.java:1294) >>>>> at >>>>> org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDel >>>>> egate.java:1287) >>>>> at >>>>> org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.parseBeanDefinitions(DefaultBeanDef >>>>> initionDocumentReader.java:135) >>>>> >>>>> Which i guess is >>>>> org.ops4j.pax.wicket.internal.injection.spring.SpringNamespaceHandler >>>>> >>>>> but adding a "Import-Package : >>>>> org.ops4j.pax.wicket.internal.injection.spring" will cause: >>>>> >>>>> org.osgi.framework.BundleException: The bundle >>>>> "de.bitnoise.demo.pax-wicket-demo-web_1.0.0.SNAPSHOT [25]" could not be r >>>>> esolved. Reason: Missing Constraint: Import-Package: >>>>> org.ops4j.pax.wicket.internal.injection.spring; version="0.0.0" >>>>> at >>>>> org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverError(AbstractBundle.java: >>>>> 1317) >>>>> at >>>>> org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolutionFailureException(AbstractBundle.java:130 >>>>> 1) >>>>> at >>>>> org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:319) >>>>> at >>>>> org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:284) >>>>> at >>>>> org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:276) >>>>> at >>>>> org.eclipse.osgi.framework.internal.core.FrameworkCommandProvider._start(FrameworkCommandProvider.java:252) >>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >>>>> >>>>> any ideas? >>>>> >>>>> PS: traces use PW 0.8.0-SNAPSHOT >>>>> >>>>> Chers Rainer >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> general mailing list >>>>> [email protected] >>>>> http://lists.ops4j.org/mailman/listinfo/general >>>>> >>>>> >>>> >>>> _______________________________________________ >>>> general mailing list >>>> [email protected] >>>> http://lists.ops4j.org/mailman/listinfo/general >>>> >>>> >>> >>> _______________________________________________ >>> general mailing list >>> [email protected] >>> http://lists.ops4j.org/mailman/listinfo/general >>> >>> >> >> _______________________________________________ >> general mailing list >> [email protected] >> http://lists.ops4j.org/mailman/listinfo/general >> >> > > _______________________________________________ > general mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/general > >
_______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
