Refer the following article to get information about the new syntax. https://medium.com/@sameera.jayasoma/resolving-startup-order-of-carbon-components-in-wso2-carbon-5-0-0-497fe3287e67
On Fri, May 13, 2016 at 4:26 PM, Niranjan Karunanandham <niran...@wso2.com> wrote: > Hi Hemika, > > The startup resolver changes compatible to kernel 5.1.0-alpha2 is > available in the master branch (PR [1]) of carbon-datasources. The > carbon-datasources 1.0.0-alpha depends on the older format. > > [1] - https://github.com/wso2/carbon-datasources/pull/14 > > Regards, > Nira > > On Fri, May 13, 2016 at 4:22 PM, Hemika Kodikara <hem...@wso2.com> wrote: > >> Thanks for the response. I have changed the kernel version to >> 5.1.0-alpha2 as mentioned. The earlier error is not coming. But I am >> getting the following error. Seems like its coming from carbon-datasources. >> I checked this with m1 version and also alpha version for datasources. >> >> ========================= >> [2016-05-13 15:16:04,974] ERROR {org.wso2.carbon.core} - FrameworkEvent >> ERROR - org.wso2.carbon.core >> org.wso2.carbon.kernel.internal.startupresolver.StartOrderResolverException: >> componentName value is missing in the services registered with the key >> org.wso2.carbon.kernel.startupresolver.RequiredCapabilityListener, >> implementation class name is >> org.wso2.carbon.datasource.core.internal.DataSourceListenerComponent >> at >> org.wso2.carbon.kernel.internal.startupresolver.OSGiServiceCapabilityTracker$CapabilityServiceTrackerCustomizer.addingService(OSGiServiceCapabilityTracker.java:142) >> at >> org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:941) >> at >> org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:870) >> at >> org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:256) >> at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:229) >> at >> org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:901) >> at >> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:109) >> at >> org.eclipse.osgi.internal.framework.BundleContextImpl.dispatchEvent(BundleContextImpl.java:914) >> at >> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) >> at >> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148) >> at >> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:862) >> at >> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:801) >> at >> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:127) >> at >> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:225) >> at >> org.eclipse.osgi.internal.framework.BundleContextImpl.registerService(BundleContextImpl.java:464) >> at >> org.eclipse.equinox.internal.ds.InstanceProcess.registerService(InstanceProcess.java:536) >> at >> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:213) >> at >> org.eclipse.equinox.internal.ds.Resolver.buildNewlySatisfied(Resolver.java:473) >> at >> org.eclipse.equinox.internal.ds.Resolver.enableComponents(Resolver.java:217) >> at >> org.eclipse.equinox.internal.ds.SCRManager.performWork(SCRManager.java:816) >> at >> org.eclipse.equinox.internal.ds.SCRManager$QueuedJob.dispatch(SCRManager.java:783) >> at org.eclipse.equinox.internal.ds.WorkThread.run(WorkThread.java:89) >> at >> org.eclipse.equinox.internal.util.impl.tpt.threadpool.Executor.run(Executor.java:70) >> >> ================== >> >> Regards, >> Hemika >> >> >> Hemika Kodikara >> Software Engineer >> WSO2 Inc. >> lean . enterprise . middleware >> http://wso2.com >> >> Mobile : +94777688882 >> >> On Fri, May 13, 2016 at 3:00 PM, Niranjan Karunanandham < >> niran...@wso2.com> wrote: >> >>> Hi Hemika, >>> >>> There has been some changes to the Startup Resolver in the 5.1.0-alpha2 >>> release. Therefore IMO it would be better if you can use 5.1.0-alpha2 and >>> carbon-parent version 5. >>> >>> Regards, >>> Nira >>> >>> On Fri, May 13, 2016 at 2:51 PM, Hemika Kodikara <hem...@wso2.com> >>> wrote: >>> >>>> Hi All, >>>> >>>> I am getting this error when starting up the MB C5 pack. We are working >>>> on the released 5.0.0 version of carbon-kernel. Any idea how this error >>>> occurs and how to avoid it ? >>>> >>>> ================================ >>>> >>>> [2016-05-13 14:43:28,491] ERROR >>>> {org.wso2.carbon.kernel.internal.startupresolver.RequireCapabilityCoordinator} >>>> - Failed to initialize startup resolver. java.lang.RuntimeException: >>>> capability-name value is missing in Provide-Capability header >>>> at >>>> org.wso2.carbon.kernel.internal.startupresolver.RequireCapabilityCoordinator.getManifestElementAttribute(RequireCapabilityCoordinator.java:381) >>>> at >>>> org.wso2.carbon.kernel.internal.startupresolver.RequireCapabilityCoordinator.lambda$processManifestHeaders$21(RequireCapabilityCoordinator.java:287) >>>> at >>>> org.wso2.carbon.kernel.internal.startupresolver.RequireCapabilityCoordinator$$Lambda$36/ >>>> 2099832114.accept(Unknown Source) >>>> at >>>> java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1374) >>>> at >>>> java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:580) >>>> at >>>> org.wso2.carbon.kernel.internal.startupresolver.RequireCapabilityCoordinator.processManifestHeaders(RequireCapabilityCoordinator.java:283) >>>> at >>>> org.wso2.carbon.kernel.internal.startupresolver.RequireCapabilityCoordinator.start(RequireCapabilityCoordinator.java:120) >>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >>>> at >>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) >>>> at >>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) >>>> at java.lang.reflect.Method.invoke(Method.java:497) >>>> at >>>> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:235) >>>> at >>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146) >>>> at >>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:345) >>>> at >>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620) >>>> at >>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197) >>>> at >>>> org.eclipse.equinox.internal.ds.Resolver.buildNewlySatisfied(Resolver.java:473) >>>> at >>>> org.eclipse.equinox.internal.ds.Resolver.enableComponents(Resolver.java:217) >>>> at >>>> org.eclipse.equinox.internal.ds.SCRManager.performWork(SCRManager.java:816) >>>> at >>>> org.eclipse.equinox.internal.ds.SCRManager$QueuedJob.dispatch(SCRManager.java:783) >>>> at org.eclipse.equinox.internal.ds.WorkThread.run(WorkThread.java:89) >>>> at >>>> org.eclipse.equinox.internal.util.impl.tpt.threadpool.Executor.run(Executor.java:70) >>>> >>>> ============================= >>>> >>>> Regards, >>>> Hemika >>>> >>>> Hemika Kodikara >>>> Software Engineer >>>> WSO2 Inc. >>>> lean . enterprise . middleware >>>> http://wso2.com >>>> >>>> Mobile : +94777688882 >>>> >>> >>> >>> >>> -- >>> >>> *Niranjan Karunanandham* >>> Senior Software Engineer - WSO2 Inc. >>> WSO2 Inc.: http://www.wso2.com >>> >> >> > > > -- > > *Niranjan Karunanandham* > Senior Software Engineer - WSO2 Inc. > WSO2 Inc.: http://www.wso2.com > -- Sameera Jayasoma, Software Architect, WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://blog.sameera.org twitter: https://twitter.com/sameerajayasoma flickr: http://www.flickr.com/photos/sameera-jayasoma/collections Mobile: 0094776364456 Lean . Enterprise . Middleware
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
