You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@felix.apache.org by Robert Munteanu <ro...@apache.org> on 2013/05/28 16:52:43 UTC

SCR 1.6.2 behaviour change - services bound in an activate method are no longer bound back to the same component instance

Hi,

I've noticed a behaviour change when upgrading from SCR 1.6.0 to 1.6.2 .

In the Apache Sling project we have a component which binds service
references in its own activate method, and expects them to be bound to
itself later on ( see [0], near the end of the activate method ).

With SCR 1.6.0, these components are bound. With 1.6.2 they are not bound.

I found nothing relevant to this edge case in the OSGi Declarative
Services spec, so my question is : is this change intended or
accidental?

Thanks,

Robert


[0]: http://svn.apache.org/repos/asf/sling/trunk/bundles/servlets/post/src/main/java/org/apache/sling/servlets/post/impl/SlingPostServlet.java

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org


SCR SNAPSHOT deployed (was: SCR head rev issue with released CM)

Posted by Felix Meschberger <fm...@adobe.com>.
Hi,

Am 28.05.2013 um 23:33 schrieb David Jencks:

> The problem is the (x32) in the location of the tomcat bundle which needs to be escaped by DS.  I also discovered this and fixed in in rev 1486758 committed this morning.  You only need an updated DS bundle.  I haven't been able to upload a snapshot to apache nexus, maybe someone else has the magic mojo.

I have just deployed a 1.7-SNAPSHOT build at Rev. 1487395 to the Apache SNAPSHOT repository.

Regards
Felix
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org


RE: SCR head rev issue with released CM

Posted by Adam Purkiss <aj...@hotmail.com>.
thanks
 
The update seems to have fixed everything. Tests pass and build finishes successfully
 
I am running windows 7 64 bit with Java 64 bit 1.7.0_17-b02 at this time.
 
I to run mvn clean install though I sometimes -DskipTests if I just want to get a build done for some testing. I have increase the memory mvn has available to it as well.
 
I have mvn 3.0.5 installed
 
Appreciate the fast responses :)
 
> Subject: Re: SCR head rev issue with released CM
> From: david_jencks@yahoo.com
> Date: Tue, 28 May 2013 17:49:31 -0700
> To: users@felix.apache.org
> 
> How do you run maven?  I usually run mvn clean install and don't get the rat:check.  Anyway I think I fixed the missing license header as well (rev 1487105)
> 
> If you see the test failure again can you email me the TEST- file so I can try to see what is going on?  I haven't seen an error here in a long time.  Also knowing your environment might be interesting…. I only build on a macbook pro, java 1.6.0_45-b06-451-11M4406
> 
> many thanks
> david jencks
> 
> 
> On May 28, 2013, at 5:05 PM, Adam Purkiss <aj...@hotmail.com> wrote:
> 
> > Ah ok
> > 
> > I tried to build the latest code but it failed a unit test and the apache rat plugin complain about licenses (see the bottom of the email) so unfortunatly I was unable to test the latest changes (I had noticed after sending this email a few file changes went in.
> > 
> >> Subject: Re: SCR head rev issue with released CM
> >> From: david_jencks@yahoo.com
> >> Date: Tue, 28 May 2013 14:33:38 -0700
> >> To: users@felix.apache.org
> >> 
> >> The problem is the (x32) in the location of the tomcat bundle which needs to be escaped by DS.  I also discovered this and fixed in in rev 1486758 committed this morning.  You only need an updated DS bundle.  I haven't been able to upload a snapshot to apache nexus, maybe someone else has the magic mojo.
> >> 
> >> This is part of targeted PID support… I still need to figure out how to write some tests for it.
> >> 
> >> Your DS is not that outdated…. I only committed the problem on may 7 :-)
> >> 
> >> thanks
> >> david jencks
> >> 
> >> On May 28, 2013, at 1:44 PM, Adam Purkiss <aj...@hotmail.com> wrote:
> >> 
> >>> I have noticed that with the slightly outdated head rev of SCR which I have been using due to bug fixes in it that I now get an error logged from felix that seems to be related to the ConfigurationManager. I have not tried to update that as I was hoping not to have to get head revs of everything inorder to to a few scr bug fixes and I have not seen any issues other than the below log message. I was wondering if others had seen it and if I really can just ignore it for the moment or should I be deploying the latest CM code to get changes it has that SCR has started to make sure of?
> >>> 
> >>> DEBUG: WIRE: [143.0] osgi.wiring.package; (&(osgi.wiring.package=org.apache.commons.httpclient.params)(version
> >>>> =3.1.0)(!(version>=4.0.0))) -> [71.1]
> >>> DEBUG: WIRE: [143.0] osgi.wiring.package; (&(osgi.wiring.package=org.osgi.framework)(version>=1.7.0)(!(version
> >>>> =2.0.0))) -> [0]
> >>> DEBUG: WIRE: [143.0] osgi.wiring.package; (&(osgi.wiring.package=org.osgi.service.component)(version>=1.2.0)(!
> >>> (version>=2.0.0))) -> [59.1]
> >>> DEBUG: WIRE: [143.0] osgi.wiring.package; (&(osgi.wiring.package=org.osgi.service.log)(version>=1.3.0)(!(versi
> >>> on>=2.0.0))) -> [128.1]
> >>> DEBUG: WIRE: [143.0] osgi.wiring.package; (&(osgi.wiring.package=org.osgi.util.tracker)(version>=1.5.0)(!(vers
> >>> ion>=2.0.0))) -> [0]
> >>> BundleEvent RESOLVED
> >>> Invalid Configuration selection filter (|(service.factoryPid=com.nuance.docimg.wedp.providers.WedpSessionCompo
> >>> nent)(service.factoryPid=com.nuance.docimg.wedp.providers.WedpSessionComponent|WedpInstanceTemplateImpl.XeroxE
> >>> CSP-10.16.2.83)(service.factoryPid=com.nuance.docimg.wedp.providers.WedpSessionComponent|WedpInstanceTemplateI
> >>> mpl.XeroxECSP-10.16.2.83|1.0.0)(service.factoryPid=com.nuance.docimg.wedp.providers.WedpSessionComponent|WedpI
> >>> nstanceTemplateImpl.XeroxECSP-10.16.2.83|1.0.0|file:/C:/tools/apache-tomcat-7.0.39(x32)/webapps/DwsMain/WEB-IN
> >>> F/wedptemplate/WedpInstanceTemplateImpl.XeroxECSP-10.16.2.83.jar))
> >>> org.apache.felix.log.LogException: org.osgi.framework.InvalidSyntaxException: Unknown operator: : (|(service.f
> >>> actoryPid=com.nuance.docimg.wedp.providers.WedpSessionComponent)(service.factoryPid=com.nuance.docimg.wedp.pro
> >>> viders.WedpSessionComponent|WedpInstanceTemplateImpl.XeroxECSP-10.16.2.83)(service.factoryPid=com.nuance.docim
> >>> g.wedp.providers.WedpSessionComponent|WedpInstanceTemplateImpl.XeroxECSP-10.16.2.83|1.0.0)(service.factoryPid=
> >>> com.nuance.docimg.wedp.providers.WedpSessionComponent|WedpInstanceTemplateImpl.XeroxECSP-10.16.2.83|1.0.0|file
> >>> :/C:/tools/apache-tomcat-7.0.39(x32)/webapps/DwsMain/WEB-INF/wedptemplate/WedpInstanceTemplateImpl.XeroxECSP-1
> >>> 0.16.2.83.jar))
> >>>       at org.apache.felix.framework.FilterImpl.<init>(FilterImpl.java:51)
> >>>       at org.apache.felix.framework.BundleContextImpl.createFilter(BundleContextImpl.java:132)
> >>>       at org.apache.felix.cm.impl.ConfigurationManager.listConfigurations(ConfigurationManager.java:636)
> >>>       at org.apache.felix.cm.impl.ConfigurationAdminImpl.listConfigurations(ConfigurationAdminImpl.java:169)
> >>>       at org.apache.felix.scr.impl.config.ConfigurationSupport.findConfigurations(ConfigurationSupport.java:
> >>> 578)
> >>>       at org.apache.felix.scr.impl.config.ConfigurationSupport.findFactoryConfigurations(ConfigurationSuppor
> >>> t.java:526)
> >>>       at org.apache.felix.scr.impl.config.ConfigurationSupport.configureComponentHolder(ConfigurationSupport
> >>> .java:124)
> >>>       at org.apache.felix.scr.impl.ComponentRegistry.registerComponentHolder(ComponentRegistry.java:421)
> >>>       at org.apache.felix.scr.impl.BundleComponentActivator.loadDescriptor(BundleComponentActivator.java:263
> >>> )
> >>>       at org.apache.felix.scr.impl.BundleComponentActivator.initialize(BundleComponentActivator.java:153)
> >>>       at org.apache.felix.scr.impl.BundleComponentActivator.<init>(BundleComponentActivator.java:115)
> >>>       at org.apache.felix.scr.impl.Activator.loadComponents(Activator.java:261)
> >>>       at org.apache.felix.scr.impl.Activator.bundleChanged(Activator.java:180)
> >>>       at org.apache.felix.framework.util.EventDispatcher.invokeBundleListenerCallback(EventDispatcher.java:8
> >>> 68)
> >>>       at org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:789)
> >>>       at org.apache.felix.framework.util.EventDispatcher.fireBundleEvent(EventDispatcher.java:514)
> >>>       at org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:4403)
> >>>       at org.apache.felix.framework.Felix.startBundle(Felix.java:2092)
> >>>       at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:955)
> >>>       at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:942)
> >>>       at com.nuance.docimg.dws.xerox.devicelifecycleprovider.impl.XeroxDeviceLifecycleProvider.add(XeroxDevi
> >>> ceLifecycleProvider.java:168)
> >>>       at com.nuance.docimg.dws.core.devicelifecyclemanager.impl.DeviceLifecycleService.add(DeviceLifecycleSe
> >>> rvice.java:435)
> >>>       at com.nuance.docimg.dws.core.devicelifecyclemanager.impl.DeviceLifecycleService.add(DeviceLifecycleSe
> >>> rvice.java:465)
> >>>       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >>>       at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> >>>       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> >>>       at java.lang.reflect.Method.invoke(Method.java:601)
> >>>       at org.apache.felix.gogo.runtime.Reflective.invoke(Reflective.java:137)
> >>>       at org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:82)
> >>>       at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:477)
> >>>       at org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:403)
> >>>       at org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)
> >>>       at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)
> >>>       at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)
> >>>       at org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:89)
> >>>       at org.apache.felix.gogo.shell.Console.run(Console.java:62)
> >>>       at org.apache.felix.gogo.shell.Shell.console(Shell.java:203)
> >>>       at org.apache.felix.gogo.shell.Shell.gosh(Shell.java:128)
> >>>       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >>>       at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> >>>       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> >>>       at java.lang.reflect.Method.invoke(Method.java:601)
> >>>       at org.apache.felix.gogo.runtime.Reflective.invoke(Reflective.java:137)
> >>>       at org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:82)
> >>>       at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:477)
> >>>       at org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:403)
> >>>       at org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)
> >>>       at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)
> >>>       at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)
> >>>       at org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:89)
> >>>       at org.apache.felix.gogo.shell.Activator.run(Activator.java:75)
> >>>       at java.lang.Thread.run(Thread.java:722)
> >>> Invalid Configuration selection filter (|(service.pid=com.nuance.docimg.wedp.providers.WedpSessionComponent)(s
> >>> ervice.pid=com.nuance.docimg.wedp.providers.WedpSessionComponent|WedpInstanceTemplateImpl.XeroxECSP-10.16.2.83
> >>> )(service.pid=com.nuance.docimg.wedp.providers.WedpSessionComponent|WedpInstanceTemplateImpl.XeroxECSP-10.16.2
> >>> .83|1.0.0)(service.pid=com.nuance.docimg.wedp.providers.WedpSessionComponent|WedpInstanceTemplateImpl.XeroxECS
> >>> P-10.16.2.83|1.0.0|file:/C:/tools/apache-tomcat-7.0.39(x32)/webapps/DwsMain/WEB-INF/wedptemplate/WedpInstanceT
> >>> emplateImpl.XeroxECSP-10.16.2.83.jar))
> >>> org.apache.felix.log.LogException: org.osgi.framework.InvalidSyntaxException: Unknown operator: : (|(service.p
> >>> id=com.nuance.docimg.wedp.providers.WedpSessionComponent)(service.pid=com.nuance.docimg.wedp.providers.WedpSes
> >>> sionComponent|WedpInstanceTemplateImpl.XeroxECSP-10.16.2.83)(service.pid=com.nuance.docimg.wedp.providers.Wedp
> >>> SessionComponent|WedpInstanceTemplateImpl.XeroxECSP-10.16.2.83|1.0.0)(service.pid=com.nuance.docimg.wedp.provi
> >>> ders.WedpSessionComponent|WedpInstanceTemplateImpl.XeroxECSP-10.16.2.83|1.0.0|file:/C:/tools/apache-tomcat-7.0
> >>> .39(x32)/webapps/DwsMain/WEB-INF/wedptemplate/WedpInstanceTemplateImpl.XeroxECSP-10.16.2.83.jar))
> >>>       at org.apache.felix.framework.FilterImpl.<init>(FilterImpl.java:51)
> >>>       at org.apache.felix.framework.BundleContextImpl.createFilter(BundleContextImpl.java:132)
> >>>       at org.apache.felix.cm.impl.ConfigurationManager.listConfigurations(ConfigurationManager.java:636)
> >>>       at org.apache.felix.cm.impl.ConfigurationAdminImpl.listConfigurations(ConfigurationAdminImpl.java:169)
> >>>       at org.apache.felix.scr.impl.config.ConfigurationSupport.findConfigurations(ConfigurationSupport.java:
> >>> 578)
> >>>       at org.apache.felix.scr.impl.config.ConfigurationSupport.findSingletonConfiguration(ConfigurationSuppo
> >>> rt.java:491)
> >>>       at org.apache.felix.scr.impl.config.ConfigurationSupport.configureComponentHolder(ConfigurationSupport
> >>> .java:140)
> >>>       at org.apache.felix.scr.impl.ComponentRegistry.registerComponentHolder(ComponentRegistry.java:421)
> >>>       at org.apache.felix.scr.impl.BundleComponentActivator.loadDescriptor(BundleComponentActivator.java:263
> >>> )
> >>>       at org.apache.felix.scr.impl.BundleComponentActivator.initialize(BundleComponentActivator.java:153)
> >>>       at org.apache.felix.scr.impl.BundleComponentActivator.<init>(BundleComponentActivator.java:115)
> >>>       at org.apache.felix.scr.impl.Activator.loadComponents(Activator.java:261)
> >>>       at org.apache.felix.scr.impl.Activator.bundleChanged(Activator.java:180)
> >>>       at org.apache.felix.framework.util.EventDispatcher.invokeBundleListenerCallback(EventDispatcher.java:8
> >>> 68)
> >>>       at org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:789)
> >>>       at org.apache.felix.framework.util.EventDispatcher.fireBundleEvent(EventDispatcher.java:514)
> >>>       at org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:4403)
> >>>       at org.apache.felix.framework.Felix.startBundle(Felix.java:2092)
> >>>       at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:955)
> >>>       at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:942)
> >>>       at com.nuance.docimg.dws.xerox.devicelifecycleprovider.impl.XeroxDeviceLifecycleProvider.add(XeroxDevi
> >>> ceLifecycleProvider.java:168)
> >>>       at com.nuance.docimg.dws.core.devicelifecyclemanager.impl.DeviceLifecycleService.add(DeviceLifecycleSe
> >>> rvice.java:435)
> >>>       at com.nuance.docimg.dws.core.devicelifecyclemanager.impl.DeviceLifecycleService.add(DeviceLifecycleSe
> >>> rvice.java:465)
> >>>       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >>>       at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> >>>       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> >>>       at java.lang.reflect.Method.invoke(Method.java:601)
> >>>       at org.apache.felix.gogo.runtime.Reflective.invoke(Reflective.java:137)
> >>>       at org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:82)
> >>>       at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:477)
> >>>       at org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:403)
> >>>       at org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)
> >>>       at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)
> >>>       at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)
> >>>       at org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:89)
> >>>       at org.apache.felix.gogo.shell.Console.run(Console.java:62)
> >>>       at org.apache.felix.gogo.shell.Shell.console(Shell.java:203)
> >>>       at org.apache.felix.gogo.shell.Shell.gosh(Shell.java:128)
> >>>       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >>>       at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> >>>       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> >>>       at java.lang.reflect.Method.invoke(Method.java:601)
> >>>       at org.apache.felix.gogo.runtime.Reflective.invoke(Reflective.java:137)
> >>>       at org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:82)
> >>>       at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:477)
> >>>       at org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:403)
> >>>       at org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)
> >>>       at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)
> >>>       at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)
> >>>       at org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:89)
> >>>       at org.apache.felix.gogo.shell.Activator.run(Activator.java:75)
> >>>       at java.lang.Thread.run(Thread.java:722)
> >>> {log=DwsCoreImpl.DwsCoreEnvironment.37}class com.nuance.docimg.dws.core.environment.impl.DwsCoreEnvironment.ge
> >>> tTemplateInstallPath(): Gogo shell: Template found at: C:\tools\apache-tomcat-7.0.39(x32)\webapps\DwsMain\WEB-
> >>> INF\wedptemplate\WedpInstanceTemplateImpl.jar
> >>> 
> >>> 
> >>> Note that when I tried to update to the latest code I had a test failure and if I skip the unit tests it just fails due to aapche-rat licenes. I have the test failure and apache rat error below.
> >>> 
> >>> log level: 2 D=16:36:20,606 T=Thread[FelixDispatchQueue,5,main]: FrameworkEvent:
> >>> PACKAGE REFRESHED
> >>> [org.ops4j.exec.DefaultJavaRunner] : org.ops4j.pax.logging.pax-logging-api[org.o
> >>> ps4j.pax.swissbox.extender.BundleWatcherShutdown in progress...
> >>> ] : Releasing bundle [org.ops4j.pax.exam.invoker.junit]
> >>> [org.ops4j.exec.DefaultJavaRunner] : Unwrapping stream I/O.
> >>> [org.ops4j.exec.DefaultJavaRunner] : Platform has been shutdown.
> >>> Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 9.575 sec
> >>> Results :
> >>> Tests in error:
> >>> test_concurrent_injection_with_bundleContext:Felix3680_2Test.test_concurrent_i
> >>> njection_with_bundleContext:org.ops4j.pax.exam.forked.ForkedTestContainer@effaa(
> >>> org.apache.felix.scr.integration.Felix3680_2Test)
> >>> Tests run: 91, Failures: 0, Errors: 1, Skipped: 0
> >>> [WARNING] File encoding has not been set, using platform encoding Cp1252, i.e. b
> >>> uild is platform dependent!
> >>> [INFO]
> >>> [INFO] --- apache-rat-plugin:0.7:check (default) @ org.apache.felix.scr ---
> >>> [INFO] Exclude: src/main/appended-resources/**
> >>> [INFO] ------------------------------------------------------------------------
> >>> [INFO] BUILD FAILURE
> >>> [INFO] ------------------------------------------------------------------------
> >>> [INFO] Total time: 7:57.548s
> >>> [INFO] Finished at: Tue May 28 16:36:23 EDT 2013
> >>> [INFO] Final Memory: 14M/457M
> >>> [INFO] ------------------------------------------------------------------------
> >>> [ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.7:check (defau
> >>> lt) on project org.apache.felix.scr: Too many unapproved licenses: 1 -> [Help 1]
> >>> 		 	   		  
> >> 
> >> 
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> >> For additional commands, e-mail: users-help@felix.apache.org
> >> 
> > 		 	   		  
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
> 
 		 	   		  

Re: SCR head rev issue with released CM

Posted by David Jencks <da...@yahoo.com>.
How do you run maven?  I usually run mvn clean install and don't get the rat:check.  Anyway I think I fixed the missing license header as well (rev 1487105)

If you see the test failure again can you email me the TEST- file so I can try to see what is going on?  I haven't seen an error here in a long time.  Also knowing your environment might be interesting…. I only build on a macbook pro, java 1.6.0_45-b06-451-11M4406

many thanks
david jencks


On May 28, 2013, at 5:05 PM, Adam Purkiss <aj...@hotmail.com> wrote:

> Ah ok
> 
> I tried to build the latest code but it failed a unit test and the apache rat plugin complain about licenses (see the bottom of the email) so unfortunatly I was unable to test the latest changes (I had noticed after sending this email a few file changes went in.
> 
>> Subject: Re: SCR head rev issue with released CM
>> From: david_jencks@yahoo.com
>> Date: Tue, 28 May 2013 14:33:38 -0700
>> To: users@felix.apache.org
>> 
>> The problem is the (x32) in the location of the tomcat bundle which needs to be escaped by DS.  I also discovered this and fixed in in rev 1486758 committed this morning.  You only need an updated DS bundle.  I haven't been able to upload a snapshot to apache nexus, maybe someone else has the magic mojo.
>> 
>> This is part of targeted PID support… I still need to figure out how to write some tests for it.
>> 
>> Your DS is not that outdated…. I only committed the problem on may 7 :-)
>> 
>> thanks
>> david jencks
>> 
>> On May 28, 2013, at 1:44 PM, Adam Purkiss <aj...@hotmail.com> wrote:
>> 
>>> I have noticed that with the slightly outdated head rev of SCR which I have been using due to bug fixes in it that I now get an error logged from felix that seems to be related to the ConfigurationManager. I have not tried to update that as I was hoping not to have to get head revs of everything inorder to to a few scr bug fixes and I have not seen any issues other than the below log message. I was wondering if others had seen it and if I really can just ignore it for the moment or should I be deploying the latest CM code to get changes it has that SCR has started to make sure of?
>>> 
>>> DEBUG: WIRE: [143.0] osgi.wiring.package; (&(osgi.wiring.package=org.apache.commons.httpclient.params)(version
>>>> =3.1.0)(!(version>=4.0.0))) -> [71.1]
>>> DEBUG: WIRE: [143.0] osgi.wiring.package; (&(osgi.wiring.package=org.osgi.framework)(version>=1.7.0)(!(version
>>>> =2.0.0))) -> [0]
>>> DEBUG: WIRE: [143.0] osgi.wiring.package; (&(osgi.wiring.package=org.osgi.service.component)(version>=1.2.0)(!
>>> (version>=2.0.0))) -> [59.1]
>>> DEBUG: WIRE: [143.0] osgi.wiring.package; (&(osgi.wiring.package=org.osgi.service.log)(version>=1.3.0)(!(versi
>>> on>=2.0.0))) -> [128.1]
>>> DEBUG: WIRE: [143.0] osgi.wiring.package; (&(osgi.wiring.package=org.osgi.util.tracker)(version>=1.5.0)(!(vers
>>> ion>=2.0.0))) -> [0]
>>> BundleEvent RESOLVED
>>> Invalid Configuration selection filter (|(service.factoryPid=com.nuance.docimg.wedp.providers.WedpSessionCompo
>>> nent)(service.factoryPid=com.nuance.docimg.wedp.providers.WedpSessionComponent|WedpInstanceTemplateImpl.XeroxE
>>> CSP-10.16.2.83)(service.factoryPid=com.nuance.docimg.wedp.providers.WedpSessionComponent|WedpInstanceTemplateI
>>> mpl.XeroxECSP-10.16.2.83|1.0.0)(service.factoryPid=com.nuance.docimg.wedp.providers.WedpSessionComponent|WedpI
>>> nstanceTemplateImpl.XeroxECSP-10.16.2.83|1.0.0|file:/C:/tools/apache-tomcat-7.0.39(x32)/webapps/DwsMain/WEB-IN
>>> F/wedptemplate/WedpInstanceTemplateImpl.XeroxECSP-10.16.2.83.jar))
>>> org.apache.felix.log.LogException: org.osgi.framework.InvalidSyntaxException: Unknown operator: : (|(service.f
>>> actoryPid=com.nuance.docimg.wedp.providers.WedpSessionComponent)(service.factoryPid=com.nuance.docimg.wedp.pro
>>> viders.WedpSessionComponent|WedpInstanceTemplateImpl.XeroxECSP-10.16.2.83)(service.factoryPid=com.nuance.docim
>>> g.wedp.providers.WedpSessionComponent|WedpInstanceTemplateImpl.XeroxECSP-10.16.2.83|1.0.0)(service.factoryPid=
>>> com.nuance.docimg.wedp.providers.WedpSessionComponent|WedpInstanceTemplateImpl.XeroxECSP-10.16.2.83|1.0.0|file
>>> :/C:/tools/apache-tomcat-7.0.39(x32)/webapps/DwsMain/WEB-INF/wedptemplate/WedpInstanceTemplateImpl.XeroxECSP-1
>>> 0.16.2.83.jar))
>>>       at org.apache.felix.framework.FilterImpl.<init>(FilterImpl.java:51)
>>>       at org.apache.felix.framework.BundleContextImpl.createFilter(BundleContextImpl.java:132)
>>>       at org.apache.felix.cm.impl.ConfigurationManager.listConfigurations(ConfigurationManager.java:636)
>>>       at org.apache.felix.cm.impl.ConfigurationAdminImpl.listConfigurations(ConfigurationAdminImpl.java:169)
>>>       at org.apache.felix.scr.impl.config.ConfigurationSupport.findConfigurations(ConfigurationSupport.java:
>>> 578)
>>>       at org.apache.felix.scr.impl.config.ConfigurationSupport.findFactoryConfigurations(ConfigurationSuppor
>>> t.java:526)
>>>       at org.apache.felix.scr.impl.config.ConfigurationSupport.configureComponentHolder(ConfigurationSupport
>>> .java:124)
>>>       at org.apache.felix.scr.impl.ComponentRegistry.registerComponentHolder(ComponentRegistry.java:421)
>>>       at org.apache.felix.scr.impl.BundleComponentActivator.loadDescriptor(BundleComponentActivator.java:263
>>> )
>>>       at org.apache.felix.scr.impl.BundleComponentActivator.initialize(BundleComponentActivator.java:153)
>>>       at org.apache.felix.scr.impl.BundleComponentActivator.<init>(BundleComponentActivator.java:115)
>>>       at org.apache.felix.scr.impl.Activator.loadComponents(Activator.java:261)
>>>       at org.apache.felix.scr.impl.Activator.bundleChanged(Activator.java:180)
>>>       at org.apache.felix.framework.util.EventDispatcher.invokeBundleListenerCallback(EventDispatcher.java:8
>>> 68)
>>>       at org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:789)
>>>       at org.apache.felix.framework.util.EventDispatcher.fireBundleEvent(EventDispatcher.java:514)
>>>       at org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:4403)
>>>       at org.apache.felix.framework.Felix.startBundle(Felix.java:2092)
>>>       at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:955)
>>>       at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:942)
>>>       at com.nuance.docimg.dws.xerox.devicelifecycleprovider.impl.XeroxDeviceLifecycleProvider.add(XeroxDevi
>>> ceLifecycleProvider.java:168)
>>>       at com.nuance.docimg.dws.core.devicelifecyclemanager.impl.DeviceLifecycleService.add(DeviceLifecycleSe
>>> rvice.java:435)
>>>       at com.nuance.docimg.dws.core.devicelifecyclemanager.impl.DeviceLifecycleService.add(DeviceLifecycleSe
>>> rvice.java:465)
>>>       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>       at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>       at java.lang.reflect.Method.invoke(Method.java:601)
>>>       at org.apache.felix.gogo.runtime.Reflective.invoke(Reflective.java:137)
>>>       at org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:82)
>>>       at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:477)
>>>       at org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:403)
>>>       at org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)
>>>       at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)
>>>       at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)
>>>       at org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:89)
>>>       at org.apache.felix.gogo.shell.Console.run(Console.java:62)
>>>       at org.apache.felix.gogo.shell.Shell.console(Shell.java:203)
>>>       at org.apache.felix.gogo.shell.Shell.gosh(Shell.java:128)
>>>       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>       at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>       at java.lang.reflect.Method.invoke(Method.java:601)
>>>       at org.apache.felix.gogo.runtime.Reflective.invoke(Reflective.java:137)
>>>       at org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:82)
>>>       at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:477)
>>>       at org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:403)
>>>       at org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)
>>>       at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)
>>>       at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)
>>>       at org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:89)
>>>       at org.apache.felix.gogo.shell.Activator.run(Activator.java:75)
>>>       at java.lang.Thread.run(Thread.java:722)
>>> Invalid Configuration selection filter (|(service.pid=com.nuance.docimg.wedp.providers.WedpSessionComponent)(s
>>> ervice.pid=com.nuance.docimg.wedp.providers.WedpSessionComponent|WedpInstanceTemplateImpl.XeroxECSP-10.16.2.83
>>> )(service.pid=com.nuance.docimg.wedp.providers.WedpSessionComponent|WedpInstanceTemplateImpl.XeroxECSP-10.16.2
>>> .83|1.0.0)(service.pid=com.nuance.docimg.wedp.providers.WedpSessionComponent|WedpInstanceTemplateImpl.XeroxECS
>>> P-10.16.2.83|1.0.0|file:/C:/tools/apache-tomcat-7.0.39(x32)/webapps/DwsMain/WEB-INF/wedptemplate/WedpInstanceT
>>> emplateImpl.XeroxECSP-10.16.2.83.jar))
>>> org.apache.felix.log.LogException: org.osgi.framework.InvalidSyntaxException: Unknown operator: : (|(service.p
>>> id=com.nuance.docimg.wedp.providers.WedpSessionComponent)(service.pid=com.nuance.docimg.wedp.providers.WedpSes
>>> sionComponent|WedpInstanceTemplateImpl.XeroxECSP-10.16.2.83)(service.pid=com.nuance.docimg.wedp.providers.Wedp
>>> SessionComponent|WedpInstanceTemplateImpl.XeroxECSP-10.16.2.83|1.0.0)(service.pid=com.nuance.docimg.wedp.provi
>>> ders.WedpSessionComponent|WedpInstanceTemplateImpl.XeroxECSP-10.16.2.83|1.0.0|file:/C:/tools/apache-tomcat-7.0
>>> .39(x32)/webapps/DwsMain/WEB-INF/wedptemplate/WedpInstanceTemplateImpl.XeroxECSP-10.16.2.83.jar))
>>>       at org.apache.felix.framework.FilterImpl.<init>(FilterImpl.java:51)
>>>       at org.apache.felix.framework.BundleContextImpl.createFilter(BundleContextImpl.java:132)
>>>       at org.apache.felix.cm.impl.ConfigurationManager.listConfigurations(ConfigurationManager.java:636)
>>>       at org.apache.felix.cm.impl.ConfigurationAdminImpl.listConfigurations(ConfigurationAdminImpl.java:169)
>>>       at org.apache.felix.scr.impl.config.ConfigurationSupport.findConfigurations(ConfigurationSupport.java:
>>> 578)
>>>       at org.apache.felix.scr.impl.config.ConfigurationSupport.findSingletonConfiguration(ConfigurationSuppo
>>> rt.java:491)
>>>       at org.apache.felix.scr.impl.config.ConfigurationSupport.configureComponentHolder(ConfigurationSupport
>>> .java:140)
>>>       at org.apache.felix.scr.impl.ComponentRegistry.registerComponentHolder(ComponentRegistry.java:421)
>>>       at org.apache.felix.scr.impl.BundleComponentActivator.loadDescriptor(BundleComponentActivator.java:263
>>> )
>>>       at org.apache.felix.scr.impl.BundleComponentActivator.initialize(BundleComponentActivator.java:153)
>>>       at org.apache.felix.scr.impl.BundleComponentActivator.<init>(BundleComponentActivator.java:115)
>>>       at org.apache.felix.scr.impl.Activator.loadComponents(Activator.java:261)
>>>       at org.apache.felix.scr.impl.Activator.bundleChanged(Activator.java:180)
>>>       at org.apache.felix.framework.util.EventDispatcher.invokeBundleListenerCallback(EventDispatcher.java:8
>>> 68)
>>>       at org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:789)
>>>       at org.apache.felix.framework.util.EventDispatcher.fireBundleEvent(EventDispatcher.java:514)
>>>       at org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:4403)
>>>       at org.apache.felix.framework.Felix.startBundle(Felix.java:2092)
>>>       at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:955)
>>>       at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:942)
>>>       at com.nuance.docimg.dws.xerox.devicelifecycleprovider.impl.XeroxDeviceLifecycleProvider.add(XeroxDevi
>>> ceLifecycleProvider.java:168)
>>>       at com.nuance.docimg.dws.core.devicelifecyclemanager.impl.DeviceLifecycleService.add(DeviceLifecycleSe
>>> rvice.java:435)
>>>       at com.nuance.docimg.dws.core.devicelifecyclemanager.impl.DeviceLifecycleService.add(DeviceLifecycleSe
>>> rvice.java:465)
>>>       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>       at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>       at java.lang.reflect.Method.invoke(Method.java:601)
>>>       at org.apache.felix.gogo.runtime.Reflective.invoke(Reflective.java:137)
>>>       at org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:82)
>>>       at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:477)
>>>       at org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:403)
>>>       at org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)
>>>       at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)
>>>       at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)
>>>       at org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:89)
>>>       at org.apache.felix.gogo.shell.Console.run(Console.java:62)
>>>       at org.apache.felix.gogo.shell.Shell.console(Shell.java:203)
>>>       at org.apache.felix.gogo.shell.Shell.gosh(Shell.java:128)
>>>       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>       at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>       at java.lang.reflect.Method.invoke(Method.java:601)
>>>       at org.apache.felix.gogo.runtime.Reflective.invoke(Reflective.java:137)
>>>       at org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:82)
>>>       at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:477)
>>>       at org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:403)
>>>       at org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)
>>>       at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)
>>>       at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)
>>>       at org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:89)
>>>       at org.apache.felix.gogo.shell.Activator.run(Activator.java:75)
>>>       at java.lang.Thread.run(Thread.java:722)
>>> {log=DwsCoreImpl.DwsCoreEnvironment.37}class com.nuance.docimg.dws.core.environment.impl.DwsCoreEnvironment.ge
>>> tTemplateInstallPath(): Gogo shell: Template found at: C:\tools\apache-tomcat-7.0.39(x32)\webapps\DwsMain\WEB-
>>> INF\wedptemplate\WedpInstanceTemplateImpl.jar
>>> 
>>> 
>>> Note that when I tried to update to the latest code I had a test failure and if I skip the unit tests it just fails due to aapche-rat licenes. I have the test failure and apache rat error below.
>>> 
>>> log level: 2 D=16:36:20,606 T=Thread[FelixDispatchQueue,5,main]: FrameworkEvent:
>>> PACKAGE REFRESHED
>>> [org.ops4j.exec.DefaultJavaRunner] : org.ops4j.pax.logging.pax-logging-api[org.o
>>> ps4j.pax.swissbox.extender.BundleWatcherShutdown in progress...
>>> ] : Releasing bundle [org.ops4j.pax.exam.invoker.junit]
>>> [org.ops4j.exec.DefaultJavaRunner] : Unwrapping stream I/O.
>>> [org.ops4j.exec.DefaultJavaRunner] : Platform has been shutdown.
>>> Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 9.575 sec
>>> Results :
>>> Tests in error:
>>> test_concurrent_injection_with_bundleContext:Felix3680_2Test.test_concurrent_i
>>> njection_with_bundleContext:org.ops4j.pax.exam.forked.ForkedTestContainer@effaa(
>>> org.apache.felix.scr.integration.Felix3680_2Test)
>>> Tests run: 91, Failures: 0, Errors: 1, Skipped: 0
>>> [WARNING] File encoding has not been set, using platform encoding Cp1252, i.e. b
>>> uild is platform dependent!
>>> [INFO]
>>> [INFO] --- apache-rat-plugin:0.7:check (default) @ org.apache.felix.scr ---
>>> [INFO] Exclude: src/main/appended-resources/**
>>> [INFO] ------------------------------------------------------------------------
>>> [INFO] BUILD FAILURE
>>> [INFO] ------------------------------------------------------------------------
>>> [INFO] Total time: 7:57.548s
>>> [INFO] Finished at: Tue May 28 16:36:23 EDT 2013
>>> [INFO] Final Memory: 14M/457M
>>> [INFO] ------------------------------------------------------------------------
>>> [ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.7:check (defau
>>> lt) on project org.apache.felix.scr: Too many unapproved licenses: 1 -> [Help 1]
>>> 		 	   		  
>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>> For additional commands, e-mail: users-help@felix.apache.org
>> 
> 		 	   		  


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org


RE: SCR head rev issue with released CM

Posted by Adam Purkiss <aj...@hotmail.com>.
Ah ok
 
I tried to build the latest code but it failed a unit test and the apache rat plugin complain about licenses (see the bottom of the email) so unfortunatly I was unable to test the latest changes (I had noticed after sending this email a few file changes went in.
 
> Subject: Re: SCR head rev issue with released CM
> From: david_jencks@yahoo.com
> Date: Tue, 28 May 2013 14:33:38 -0700
> To: users@felix.apache.org
> 
> The problem is the (x32) in the location of the tomcat bundle which needs to be escaped by DS.  I also discovered this and fixed in in rev 1486758 committed this morning.  You only need an updated DS bundle.  I haven't been able to upload a snapshot to apache nexus, maybe someone else has the magic mojo.
> 
> This is part of targeted PID support… I still need to figure out how to write some tests for it.
> 
> Your DS is not that outdated…. I only committed the problem on may 7 :-)
> 
> thanks
> david jencks
> 
> On May 28, 2013, at 1:44 PM, Adam Purkiss <aj...@hotmail.com> wrote:
> 
> > I have noticed that with the slightly outdated head rev of SCR which I have been using due to bug fixes in it that I now get an error logged from felix that seems to be related to the ConfigurationManager. I have not tried to update that as I was hoping not to have to get head revs of everything inorder to to a few scr bug fixes and I have not seen any issues other than the below log message. I was wondering if others had seen it and if I really can just ignore it for the moment or should I be deploying the latest CM code to get changes it has that SCR has started to make sure of?
> > 
> > DEBUG: WIRE: [143.0] osgi.wiring.package; (&(osgi.wiring.package=org.apache.commons.httpclient.params)(version
> >> =3.1.0)(!(version>=4.0.0))) -> [71.1]
> > DEBUG: WIRE: [143.0] osgi.wiring.package; (&(osgi.wiring.package=org.osgi.framework)(version>=1.7.0)(!(version
> >> =2.0.0))) -> [0]
> > DEBUG: WIRE: [143.0] osgi.wiring.package; (&(osgi.wiring.package=org.osgi.service.component)(version>=1.2.0)(!
> > (version>=2.0.0))) -> [59.1]
> > DEBUG: WIRE: [143.0] osgi.wiring.package; (&(osgi.wiring.package=org.osgi.service.log)(version>=1.3.0)(!(versi
> > on>=2.0.0))) -> [128.1]
> > DEBUG: WIRE: [143.0] osgi.wiring.package; (&(osgi.wiring.package=org.osgi.util.tracker)(version>=1.5.0)(!(vers
> > ion>=2.0.0))) -> [0]
> > BundleEvent RESOLVED
> > Invalid Configuration selection filter (|(service.factoryPid=com.nuance.docimg.wedp.providers.WedpSessionCompo
> > nent)(service.factoryPid=com.nuance.docimg.wedp.providers.WedpSessionComponent|WedpInstanceTemplateImpl.XeroxE
> > CSP-10.16.2.83)(service.factoryPid=com.nuance.docimg.wedp.providers.WedpSessionComponent|WedpInstanceTemplateI
> > mpl.XeroxECSP-10.16.2.83|1.0.0)(service.factoryPid=com.nuance.docimg.wedp.providers.WedpSessionComponent|WedpI
> > nstanceTemplateImpl.XeroxECSP-10.16.2.83|1.0.0|file:/C:/tools/apache-tomcat-7.0.39(x32)/webapps/DwsMain/WEB-IN
> > F/wedptemplate/WedpInstanceTemplateImpl.XeroxECSP-10.16.2.83.jar))
> > org.apache.felix.log.LogException: org.osgi.framework.InvalidSyntaxException: Unknown operator: : (|(service.f
> > actoryPid=com.nuance.docimg.wedp.providers.WedpSessionComponent)(service.factoryPid=com.nuance.docimg.wedp.pro
> > viders.WedpSessionComponent|WedpInstanceTemplateImpl.XeroxECSP-10.16.2.83)(service.factoryPid=com.nuance.docim
> > g.wedp.providers.WedpSessionComponent|WedpInstanceTemplateImpl.XeroxECSP-10.16.2.83|1.0.0)(service.factoryPid=
> > com.nuance.docimg.wedp.providers.WedpSessionComponent|WedpInstanceTemplateImpl.XeroxECSP-10.16.2.83|1.0.0|file
> > :/C:/tools/apache-tomcat-7.0.39(x32)/webapps/DwsMain/WEB-INF/wedptemplate/WedpInstanceTemplateImpl.XeroxECSP-1
> > 0.16.2.83.jar))
> >        at org.apache.felix.framework.FilterImpl.<init>(FilterImpl.java:51)
> >        at org.apache.felix.framework.BundleContextImpl.createFilter(BundleContextImpl.java:132)
> >        at org.apache.felix.cm.impl.ConfigurationManager.listConfigurations(ConfigurationManager.java:636)
> >        at org.apache.felix.cm.impl.ConfigurationAdminImpl.listConfigurations(ConfigurationAdminImpl.java:169)
> >        at org.apache.felix.scr.impl.config.ConfigurationSupport.findConfigurations(ConfigurationSupport.java:
> > 578)
> >        at org.apache.felix.scr.impl.config.ConfigurationSupport.findFactoryConfigurations(ConfigurationSuppor
> > t.java:526)
> >        at org.apache.felix.scr.impl.config.ConfigurationSupport.configureComponentHolder(ConfigurationSupport
> > .java:124)
> >        at org.apache.felix.scr.impl.ComponentRegistry.registerComponentHolder(ComponentRegistry.java:421)
> >        at org.apache.felix.scr.impl.BundleComponentActivator.loadDescriptor(BundleComponentActivator.java:263
> > )
> >        at org.apache.felix.scr.impl.BundleComponentActivator.initialize(BundleComponentActivator.java:153)
> >        at org.apache.felix.scr.impl.BundleComponentActivator.<init>(BundleComponentActivator.java:115)
> >        at org.apache.felix.scr.impl.Activator.loadComponents(Activator.java:261)
> >        at org.apache.felix.scr.impl.Activator.bundleChanged(Activator.java:180)
> >        at org.apache.felix.framework.util.EventDispatcher.invokeBundleListenerCallback(EventDispatcher.java:8
> > 68)
> >        at org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:789)
> >        at org.apache.felix.framework.util.EventDispatcher.fireBundleEvent(EventDispatcher.java:514)
> >        at org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:4403)
> >        at org.apache.felix.framework.Felix.startBundle(Felix.java:2092)
> >        at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:955)
> >        at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:942)
> >        at com.nuance.docimg.dws.xerox.devicelifecycleprovider.impl.XeroxDeviceLifecycleProvider.add(XeroxDevi
> > ceLifecycleProvider.java:168)
> >        at com.nuance.docimg.dws.core.devicelifecyclemanager.impl.DeviceLifecycleService.add(DeviceLifecycleSe
> > rvice.java:435)
> >        at com.nuance.docimg.dws.core.devicelifecyclemanager.impl.DeviceLifecycleService.add(DeviceLifecycleSe
> > rvice.java:465)
> >        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> >        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> >        at java.lang.reflect.Method.invoke(Method.java:601)
> >        at org.apache.felix.gogo.runtime.Reflective.invoke(Reflective.java:137)
> >        at org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:82)
> >        at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:477)
> >        at org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:403)
> >        at org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)
> >        at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)
> >        at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)
> >        at org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:89)
> >        at org.apache.felix.gogo.shell.Console.run(Console.java:62)
> >        at org.apache.felix.gogo.shell.Shell.console(Shell.java:203)
> >        at org.apache.felix.gogo.shell.Shell.gosh(Shell.java:128)
> >        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> >        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> >        at java.lang.reflect.Method.invoke(Method.java:601)
> >        at org.apache.felix.gogo.runtime.Reflective.invoke(Reflective.java:137)
> >        at org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:82)
> >        at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:477)
> >        at org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:403)
> >        at org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)
> >        at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)
> >        at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)
> >        at org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:89)
> >        at org.apache.felix.gogo.shell.Activator.run(Activator.java:75)
> >        at java.lang.Thread.run(Thread.java:722)
> > Invalid Configuration selection filter (|(service.pid=com.nuance.docimg.wedp.providers.WedpSessionComponent)(s
> > ervice.pid=com.nuance.docimg.wedp.providers.WedpSessionComponent|WedpInstanceTemplateImpl.XeroxECSP-10.16.2.83
> > )(service.pid=com.nuance.docimg.wedp.providers.WedpSessionComponent|WedpInstanceTemplateImpl.XeroxECSP-10.16.2
> > .83|1.0.0)(service.pid=com.nuance.docimg.wedp.providers.WedpSessionComponent|WedpInstanceTemplateImpl.XeroxECS
> > P-10.16.2.83|1.0.0|file:/C:/tools/apache-tomcat-7.0.39(x32)/webapps/DwsMain/WEB-INF/wedptemplate/WedpInstanceT
> > emplateImpl.XeroxECSP-10.16.2.83.jar))
> > org.apache.felix.log.LogException: org.osgi.framework.InvalidSyntaxException: Unknown operator: : (|(service.p
> > id=com.nuance.docimg.wedp.providers.WedpSessionComponent)(service.pid=com.nuance.docimg.wedp.providers.WedpSes
> > sionComponent|WedpInstanceTemplateImpl.XeroxECSP-10.16.2.83)(service.pid=com.nuance.docimg.wedp.providers.Wedp
> > SessionComponent|WedpInstanceTemplateImpl.XeroxECSP-10.16.2.83|1.0.0)(service.pid=com.nuance.docimg.wedp.provi
> > ders.WedpSessionComponent|WedpInstanceTemplateImpl.XeroxECSP-10.16.2.83|1.0.0|file:/C:/tools/apache-tomcat-7.0
> > .39(x32)/webapps/DwsMain/WEB-INF/wedptemplate/WedpInstanceTemplateImpl.XeroxECSP-10.16.2.83.jar))
> >        at org.apache.felix.framework.FilterImpl.<init>(FilterImpl.java:51)
> >        at org.apache.felix.framework.BundleContextImpl.createFilter(BundleContextImpl.java:132)
> >        at org.apache.felix.cm.impl.ConfigurationManager.listConfigurations(ConfigurationManager.java:636)
> >        at org.apache.felix.cm.impl.ConfigurationAdminImpl.listConfigurations(ConfigurationAdminImpl.java:169)
> >        at org.apache.felix.scr.impl.config.ConfigurationSupport.findConfigurations(ConfigurationSupport.java:
> > 578)
> >        at org.apache.felix.scr.impl.config.ConfigurationSupport.findSingletonConfiguration(ConfigurationSuppo
> > rt.java:491)
> >        at org.apache.felix.scr.impl.config.ConfigurationSupport.configureComponentHolder(ConfigurationSupport
> > .java:140)
> >        at org.apache.felix.scr.impl.ComponentRegistry.registerComponentHolder(ComponentRegistry.java:421)
> >        at org.apache.felix.scr.impl.BundleComponentActivator.loadDescriptor(BundleComponentActivator.java:263
> > )
> >        at org.apache.felix.scr.impl.BundleComponentActivator.initialize(BundleComponentActivator.java:153)
> >        at org.apache.felix.scr.impl.BundleComponentActivator.<init>(BundleComponentActivator.java:115)
> >        at org.apache.felix.scr.impl.Activator.loadComponents(Activator.java:261)
> >        at org.apache.felix.scr.impl.Activator.bundleChanged(Activator.java:180)
> >        at org.apache.felix.framework.util.EventDispatcher.invokeBundleListenerCallback(EventDispatcher.java:8
> > 68)
> >        at org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:789)
> >        at org.apache.felix.framework.util.EventDispatcher.fireBundleEvent(EventDispatcher.java:514)
> >        at org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:4403)
> >        at org.apache.felix.framework.Felix.startBundle(Felix.java:2092)
> >        at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:955)
> >        at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:942)
> >        at com.nuance.docimg.dws.xerox.devicelifecycleprovider.impl.XeroxDeviceLifecycleProvider.add(XeroxDevi
> > ceLifecycleProvider.java:168)
> >        at com.nuance.docimg.dws.core.devicelifecyclemanager.impl.DeviceLifecycleService.add(DeviceLifecycleSe
> > rvice.java:435)
> >        at com.nuance.docimg.dws.core.devicelifecyclemanager.impl.DeviceLifecycleService.add(DeviceLifecycleSe
> > rvice.java:465)
> >        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> >        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> >        at java.lang.reflect.Method.invoke(Method.java:601)
> >        at org.apache.felix.gogo.runtime.Reflective.invoke(Reflective.java:137)
> >        at org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:82)
> >        at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:477)
> >        at org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:403)
> >        at org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)
> >        at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)
> >        at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)
> >        at org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:89)
> >        at org.apache.felix.gogo.shell.Console.run(Console.java:62)
> >        at org.apache.felix.gogo.shell.Shell.console(Shell.java:203)
> >        at org.apache.felix.gogo.shell.Shell.gosh(Shell.java:128)
> >        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> >        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> >        at java.lang.reflect.Method.invoke(Method.java:601)
> >        at org.apache.felix.gogo.runtime.Reflective.invoke(Reflective.java:137)
> >        at org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:82)
> >        at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:477)
> >        at org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:403)
> >        at org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)
> >        at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)
> >        at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)
> >        at org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:89)
> >        at org.apache.felix.gogo.shell.Activator.run(Activator.java:75)
> >        at java.lang.Thread.run(Thread.java:722)
> > {log=DwsCoreImpl.DwsCoreEnvironment.37}class com.nuance.docimg.dws.core.environment.impl.DwsCoreEnvironment.ge
> > tTemplateInstallPath(): Gogo shell: Template found at: C:\tools\apache-tomcat-7.0.39(x32)\webapps\DwsMain\WEB-
> > INF\wedptemplate\WedpInstanceTemplateImpl.jar
> > 
> > 
> > Note that when I tried to update to the latest code I had a test failure and if I skip the unit tests it just fails due to aapche-rat licenes. I have the test failure and apache rat error below.
> > 
> > log level: 2 D=16:36:20,606 T=Thread[FelixDispatchQueue,5,main]: FrameworkEvent:
> > PACKAGE REFRESHED
> > [org.ops4j.exec.DefaultJavaRunner] : org.ops4j.pax.logging.pax-logging-api[org.o
> > ps4j.pax.swissbox.extender.BundleWatcherShutdown in progress...
> > ] : Releasing bundle [org.ops4j.pax.exam.invoker.junit]
> > [org.ops4j.exec.DefaultJavaRunner] : Unwrapping stream I/O.
> > [org.ops4j.exec.DefaultJavaRunner] : Platform has been shutdown.
> > Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 9.575 sec
> > Results :
> > Tests in error:
> >  test_concurrent_injection_with_bundleContext:Felix3680_2Test.test_concurrent_i
> > njection_with_bundleContext:org.ops4j.pax.exam.forked.ForkedTestContainer@effaa(
> > org.apache.felix.scr.integration.Felix3680_2Test)
> > Tests run: 91, Failures: 0, Errors: 1, Skipped: 0
> > [WARNING] File encoding has not been set, using platform encoding Cp1252, i.e. b
> > uild is platform dependent!
> > [INFO]
> > [INFO] --- apache-rat-plugin:0.7:check (default) @ org.apache.felix.scr ---
> > [INFO] Exclude: src/main/appended-resources/**
> > [INFO] ------------------------------------------------------------------------
> > [INFO] BUILD FAILURE
> > [INFO] ------------------------------------------------------------------------
> > [INFO] Total time: 7:57.548s
> > [INFO] Finished at: Tue May 28 16:36:23 EDT 2013
> > [INFO] Final Memory: 14M/457M
> > [INFO] ------------------------------------------------------------------------
> > [ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.7:check (defau
> > lt) on project org.apache.felix.scr: Too many unapproved licenses: 1 -> [Help 1]
> > 		 	   		  
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
> 
 		 	   		  

Re: SCR head rev issue with released CM

Posted by David Jencks <da...@yahoo.com>.
The problem is the (x32) in the location of the tomcat bundle which needs to be escaped by DS.  I also discovered this and fixed in in rev 1486758 committed this morning.  You only need an updated DS bundle.  I haven't been able to upload a snapshot to apache nexus, maybe someone else has the magic mojo.

This is part of targeted PID support… I still need to figure out how to write some tests for it.

Your DS is not that outdated…. I only committed the problem on may 7 :-)

thanks
david jencks

On May 28, 2013, at 1:44 PM, Adam Purkiss <aj...@hotmail.com> wrote:

> I have noticed that with the slightly outdated head rev of SCR which I have been using due to bug fixes in it that I now get an error logged from felix that seems to be related to the ConfigurationManager. I have not tried to update that as I was hoping not to have to get head revs of everything inorder to to a few scr bug fixes and I have not seen any issues other than the below log message. I was wondering if others had seen it and if I really can just ignore it for the moment or should I be deploying the latest CM code to get changes it has that SCR has started to make sure of?
> 
> DEBUG: WIRE: [143.0] osgi.wiring.package; (&(osgi.wiring.package=org.apache.commons.httpclient.params)(version
>> =3.1.0)(!(version>=4.0.0))) -> [71.1]
> DEBUG: WIRE: [143.0] osgi.wiring.package; (&(osgi.wiring.package=org.osgi.framework)(version>=1.7.0)(!(version
>> =2.0.0))) -> [0]
> DEBUG: WIRE: [143.0] osgi.wiring.package; (&(osgi.wiring.package=org.osgi.service.component)(version>=1.2.0)(!
> (version>=2.0.0))) -> [59.1]
> DEBUG: WIRE: [143.0] osgi.wiring.package; (&(osgi.wiring.package=org.osgi.service.log)(version>=1.3.0)(!(versi
> on>=2.0.0))) -> [128.1]
> DEBUG: WIRE: [143.0] osgi.wiring.package; (&(osgi.wiring.package=org.osgi.util.tracker)(version>=1.5.0)(!(vers
> ion>=2.0.0))) -> [0]
> BundleEvent RESOLVED
> Invalid Configuration selection filter (|(service.factoryPid=com.nuance.docimg.wedp.providers.WedpSessionCompo
> nent)(service.factoryPid=com.nuance.docimg.wedp.providers.WedpSessionComponent|WedpInstanceTemplateImpl.XeroxE
> CSP-10.16.2.83)(service.factoryPid=com.nuance.docimg.wedp.providers.WedpSessionComponent|WedpInstanceTemplateI
> mpl.XeroxECSP-10.16.2.83|1.0.0)(service.factoryPid=com.nuance.docimg.wedp.providers.WedpSessionComponent|WedpI
> nstanceTemplateImpl.XeroxECSP-10.16.2.83|1.0.0|file:/C:/tools/apache-tomcat-7.0.39(x32)/webapps/DwsMain/WEB-IN
> F/wedptemplate/WedpInstanceTemplateImpl.XeroxECSP-10.16.2.83.jar))
> org.apache.felix.log.LogException: org.osgi.framework.InvalidSyntaxException: Unknown operator: : (|(service.f
> actoryPid=com.nuance.docimg.wedp.providers.WedpSessionComponent)(service.factoryPid=com.nuance.docimg.wedp.pro
> viders.WedpSessionComponent|WedpInstanceTemplateImpl.XeroxECSP-10.16.2.83)(service.factoryPid=com.nuance.docim
> g.wedp.providers.WedpSessionComponent|WedpInstanceTemplateImpl.XeroxECSP-10.16.2.83|1.0.0)(service.factoryPid=
> com.nuance.docimg.wedp.providers.WedpSessionComponent|WedpInstanceTemplateImpl.XeroxECSP-10.16.2.83|1.0.0|file
> :/C:/tools/apache-tomcat-7.0.39(x32)/webapps/DwsMain/WEB-INF/wedptemplate/WedpInstanceTemplateImpl.XeroxECSP-1
> 0.16.2.83.jar))
>        at org.apache.felix.framework.FilterImpl.<init>(FilterImpl.java:51)
>        at org.apache.felix.framework.BundleContextImpl.createFilter(BundleContextImpl.java:132)
>        at org.apache.felix.cm.impl.ConfigurationManager.listConfigurations(ConfigurationManager.java:636)
>        at org.apache.felix.cm.impl.ConfigurationAdminImpl.listConfigurations(ConfigurationAdminImpl.java:169)
>        at org.apache.felix.scr.impl.config.ConfigurationSupport.findConfigurations(ConfigurationSupport.java:
> 578)
>        at org.apache.felix.scr.impl.config.ConfigurationSupport.findFactoryConfigurations(ConfigurationSuppor
> t.java:526)
>        at org.apache.felix.scr.impl.config.ConfigurationSupport.configureComponentHolder(ConfigurationSupport
> .java:124)
>        at org.apache.felix.scr.impl.ComponentRegistry.registerComponentHolder(ComponentRegistry.java:421)
>        at org.apache.felix.scr.impl.BundleComponentActivator.loadDescriptor(BundleComponentActivator.java:263
> )
>        at org.apache.felix.scr.impl.BundleComponentActivator.initialize(BundleComponentActivator.java:153)
>        at org.apache.felix.scr.impl.BundleComponentActivator.<init>(BundleComponentActivator.java:115)
>        at org.apache.felix.scr.impl.Activator.loadComponents(Activator.java:261)
>        at org.apache.felix.scr.impl.Activator.bundleChanged(Activator.java:180)
>        at org.apache.felix.framework.util.EventDispatcher.invokeBundleListenerCallback(EventDispatcher.java:8
> 68)
>        at org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:789)
>        at org.apache.felix.framework.util.EventDispatcher.fireBundleEvent(EventDispatcher.java:514)
>        at org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:4403)
>        at org.apache.felix.framework.Felix.startBundle(Felix.java:2092)
>        at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:955)
>        at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:942)
>        at com.nuance.docimg.dws.xerox.devicelifecycleprovider.impl.XeroxDeviceLifecycleProvider.add(XeroxDevi
> ceLifecycleProvider.java:168)
>        at com.nuance.docimg.dws.core.devicelifecyclemanager.impl.DeviceLifecycleService.add(DeviceLifecycleSe
> rvice.java:435)
>        at com.nuance.docimg.dws.core.devicelifecyclemanager.impl.DeviceLifecycleService.add(DeviceLifecycleSe
> rvice.java:465)
>        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>        at java.lang.reflect.Method.invoke(Method.java:601)
>        at org.apache.felix.gogo.runtime.Reflective.invoke(Reflective.java:137)
>        at org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:82)
>        at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:477)
>        at org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:403)
>        at org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)
>        at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)
>        at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)
>        at org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:89)
>        at org.apache.felix.gogo.shell.Console.run(Console.java:62)
>        at org.apache.felix.gogo.shell.Shell.console(Shell.java:203)
>        at org.apache.felix.gogo.shell.Shell.gosh(Shell.java:128)
>        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>        at java.lang.reflect.Method.invoke(Method.java:601)
>        at org.apache.felix.gogo.runtime.Reflective.invoke(Reflective.java:137)
>        at org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:82)
>        at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:477)
>        at org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:403)
>        at org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)
>        at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)
>        at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)
>        at org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:89)
>        at org.apache.felix.gogo.shell.Activator.run(Activator.java:75)
>        at java.lang.Thread.run(Thread.java:722)
> Invalid Configuration selection filter (|(service.pid=com.nuance.docimg.wedp.providers.WedpSessionComponent)(s
> ervice.pid=com.nuance.docimg.wedp.providers.WedpSessionComponent|WedpInstanceTemplateImpl.XeroxECSP-10.16.2.83
> )(service.pid=com.nuance.docimg.wedp.providers.WedpSessionComponent|WedpInstanceTemplateImpl.XeroxECSP-10.16.2
> .83|1.0.0)(service.pid=com.nuance.docimg.wedp.providers.WedpSessionComponent|WedpInstanceTemplateImpl.XeroxECS
> P-10.16.2.83|1.0.0|file:/C:/tools/apache-tomcat-7.0.39(x32)/webapps/DwsMain/WEB-INF/wedptemplate/WedpInstanceT
> emplateImpl.XeroxECSP-10.16.2.83.jar))
> org.apache.felix.log.LogException: org.osgi.framework.InvalidSyntaxException: Unknown operator: : (|(service.p
> id=com.nuance.docimg.wedp.providers.WedpSessionComponent)(service.pid=com.nuance.docimg.wedp.providers.WedpSes
> sionComponent|WedpInstanceTemplateImpl.XeroxECSP-10.16.2.83)(service.pid=com.nuance.docimg.wedp.providers.Wedp
> SessionComponent|WedpInstanceTemplateImpl.XeroxECSP-10.16.2.83|1.0.0)(service.pid=com.nuance.docimg.wedp.provi
> ders.WedpSessionComponent|WedpInstanceTemplateImpl.XeroxECSP-10.16.2.83|1.0.0|file:/C:/tools/apache-tomcat-7.0
> .39(x32)/webapps/DwsMain/WEB-INF/wedptemplate/WedpInstanceTemplateImpl.XeroxECSP-10.16.2.83.jar))
>        at org.apache.felix.framework.FilterImpl.<init>(FilterImpl.java:51)
>        at org.apache.felix.framework.BundleContextImpl.createFilter(BundleContextImpl.java:132)
>        at org.apache.felix.cm.impl.ConfigurationManager.listConfigurations(ConfigurationManager.java:636)
>        at org.apache.felix.cm.impl.ConfigurationAdminImpl.listConfigurations(ConfigurationAdminImpl.java:169)
>        at org.apache.felix.scr.impl.config.ConfigurationSupport.findConfigurations(ConfigurationSupport.java:
> 578)
>        at org.apache.felix.scr.impl.config.ConfigurationSupport.findSingletonConfiguration(ConfigurationSuppo
> rt.java:491)
>        at org.apache.felix.scr.impl.config.ConfigurationSupport.configureComponentHolder(ConfigurationSupport
> .java:140)
>        at org.apache.felix.scr.impl.ComponentRegistry.registerComponentHolder(ComponentRegistry.java:421)
>        at org.apache.felix.scr.impl.BundleComponentActivator.loadDescriptor(BundleComponentActivator.java:263
> )
>        at org.apache.felix.scr.impl.BundleComponentActivator.initialize(BundleComponentActivator.java:153)
>        at org.apache.felix.scr.impl.BundleComponentActivator.<init>(BundleComponentActivator.java:115)
>        at org.apache.felix.scr.impl.Activator.loadComponents(Activator.java:261)
>        at org.apache.felix.scr.impl.Activator.bundleChanged(Activator.java:180)
>        at org.apache.felix.framework.util.EventDispatcher.invokeBundleListenerCallback(EventDispatcher.java:8
> 68)
>        at org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:789)
>        at org.apache.felix.framework.util.EventDispatcher.fireBundleEvent(EventDispatcher.java:514)
>        at org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:4403)
>        at org.apache.felix.framework.Felix.startBundle(Felix.java:2092)
>        at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:955)
>        at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:942)
>        at com.nuance.docimg.dws.xerox.devicelifecycleprovider.impl.XeroxDeviceLifecycleProvider.add(XeroxDevi
> ceLifecycleProvider.java:168)
>        at com.nuance.docimg.dws.core.devicelifecyclemanager.impl.DeviceLifecycleService.add(DeviceLifecycleSe
> rvice.java:435)
>        at com.nuance.docimg.dws.core.devicelifecyclemanager.impl.DeviceLifecycleService.add(DeviceLifecycleSe
> rvice.java:465)
>        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>        at java.lang.reflect.Method.invoke(Method.java:601)
>        at org.apache.felix.gogo.runtime.Reflective.invoke(Reflective.java:137)
>        at org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:82)
>        at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:477)
>        at org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:403)
>        at org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)
>        at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)
>        at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)
>        at org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:89)
>        at org.apache.felix.gogo.shell.Console.run(Console.java:62)
>        at org.apache.felix.gogo.shell.Shell.console(Shell.java:203)
>        at org.apache.felix.gogo.shell.Shell.gosh(Shell.java:128)
>        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>        at java.lang.reflect.Method.invoke(Method.java:601)
>        at org.apache.felix.gogo.runtime.Reflective.invoke(Reflective.java:137)
>        at org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:82)
>        at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:477)
>        at org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:403)
>        at org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)
>        at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)
>        at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)
>        at org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:89)
>        at org.apache.felix.gogo.shell.Activator.run(Activator.java:75)
>        at java.lang.Thread.run(Thread.java:722)
> {log=DwsCoreImpl.DwsCoreEnvironment.37}class com.nuance.docimg.dws.core.environment.impl.DwsCoreEnvironment.ge
> tTemplateInstallPath(): Gogo shell: Template found at: C:\tools\apache-tomcat-7.0.39(x32)\webapps\DwsMain\WEB-
> INF\wedptemplate\WedpInstanceTemplateImpl.jar
> 
> 
> Note that when I tried to update to the latest code I had a test failure and if I skip the unit tests it just fails due to aapche-rat licenes. I have the test failure and apache rat error below.
> 
> log level: 2 D=16:36:20,606 T=Thread[FelixDispatchQueue,5,main]: FrameworkEvent:
> PACKAGE REFRESHED
> [org.ops4j.exec.DefaultJavaRunner] : org.ops4j.pax.logging.pax-logging-api[org.o
> ps4j.pax.swissbox.extender.BundleWatcherShutdown in progress...
> ] : Releasing bundle [org.ops4j.pax.exam.invoker.junit]
> [org.ops4j.exec.DefaultJavaRunner] : Unwrapping stream I/O.
> [org.ops4j.exec.DefaultJavaRunner] : Platform has been shutdown.
> Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 9.575 sec
> Results :
> Tests in error:
>  test_concurrent_injection_with_bundleContext:Felix3680_2Test.test_concurrent_i
> njection_with_bundleContext:org.ops4j.pax.exam.forked.ForkedTestContainer@effaa(
> org.apache.felix.scr.integration.Felix3680_2Test)
> Tests run: 91, Failures: 0, Errors: 1, Skipped: 0
> [WARNING] File encoding has not been set, using platform encoding Cp1252, i.e. b
> uild is platform dependent!
> [INFO]
> [INFO] --- apache-rat-plugin:0.7:check (default) @ org.apache.felix.scr ---
> [INFO] Exclude: src/main/appended-resources/**
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 7:57.548s
> [INFO] Finished at: Tue May 28 16:36:23 EDT 2013
> [INFO] Final Memory: 14M/457M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.7:check (defau
> lt) on project org.apache.felix.scr: Too many unapproved licenses: 1 -> [Help 1]
> 		 	   		  


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org


SCR head rev issue with released CM

Posted by Adam Purkiss <aj...@hotmail.com>.
I have noticed that with the slightly outdated head rev of SCR which I have been using due to bug fixes in it that I now get an error logged from felix that seems to be related to the ConfigurationManager. I have not tried to update that as I was hoping not to have to get head revs of everything inorder to to a few scr bug fixes and I have not seen any issues other than the below log message. I was wondering if others had seen it and if I really can just ignore it for the moment or should I be deploying the latest CM code to get changes it has that SCR has started to make sure of?
 
DEBUG: WIRE: [143.0] osgi.wiring.package; (&(osgi.wiring.package=org.apache.commons.httpclient.params)(version
>=3.1.0)(!(version>=4.0.0))) -> [71.1]
DEBUG: WIRE: [143.0] osgi.wiring.package; (&(osgi.wiring.package=org.osgi.framework)(version>=1.7.0)(!(version
>=2.0.0))) -> [0]
DEBUG: WIRE: [143.0] osgi.wiring.package; (&(osgi.wiring.package=org.osgi.service.component)(version>=1.2.0)(!
(version>=2.0.0))) -> [59.1]
DEBUG: WIRE: [143.0] osgi.wiring.package; (&(osgi.wiring.package=org.osgi.service.log)(version>=1.3.0)(!(versi
on>=2.0.0))) -> [128.1]
DEBUG: WIRE: [143.0] osgi.wiring.package; (&(osgi.wiring.package=org.osgi.util.tracker)(version>=1.5.0)(!(vers
ion>=2.0.0))) -> [0]
BundleEvent RESOLVED
Invalid Configuration selection filter (|(service.factoryPid=com.nuance.docimg.wedp.providers.WedpSessionCompo
nent)(service.factoryPid=com.nuance.docimg.wedp.providers.WedpSessionComponent|WedpInstanceTemplateImpl.XeroxE
CSP-10.16.2.83)(service.factoryPid=com.nuance.docimg.wedp.providers.WedpSessionComponent|WedpInstanceTemplateI
mpl.XeroxECSP-10.16.2.83|1.0.0)(service.factoryPid=com.nuance.docimg.wedp.providers.WedpSessionComponent|WedpI
nstanceTemplateImpl.XeroxECSP-10.16.2.83|1.0.0|file:/C:/tools/apache-tomcat-7.0.39(x32)/webapps/DwsMain/WEB-IN
F/wedptemplate/WedpInstanceTemplateImpl.XeroxECSP-10.16.2.83.jar))
org.apache.felix.log.LogException: org.osgi.framework.InvalidSyntaxException: Unknown operator: : (|(service.f
actoryPid=com.nuance.docimg.wedp.providers.WedpSessionComponent)(service.factoryPid=com.nuance.docimg.wedp.pro
viders.WedpSessionComponent|WedpInstanceTemplateImpl.XeroxECSP-10.16.2.83)(service.factoryPid=com.nuance.docim
g.wedp.providers.WedpSessionComponent|WedpInstanceTemplateImpl.XeroxECSP-10.16.2.83|1.0.0)(service.factoryPid=
com.nuance.docimg.wedp.providers.WedpSessionComponent|WedpInstanceTemplateImpl.XeroxECSP-10.16.2.83|1.0.0|file
:/C:/tools/apache-tomcat-7.0.39(x32)/webapps/DwsMain/WEB-INF/wedptemplate/WedpInstanceTemplateImpl.XeroxECSP-1
0.16.2.83.jar))
        at org.apache.felix.framework.FilterImpl.<init>(FilterImpl.java:51)
        at org.apache.felix.framework.BundleContextImpl.createFilter(BundleContextImpl.java:132)
        at org.apache.felix.cm.impl.ConfigurationManager.listConfigurations(ConfigurationManager.java:636)
        at org.apache.felix.cm.impl.ConfigurationAdminImpl.listConfigurations(ConfigurationAdminImpl.java:169)
        at org.apache.felix.scr.impl.config.ConfigurationSupport.findConfigurations(ConfigurationSupport.java:
578)
        at org.apache.felix.scr.impl.config.ConfigurationSupport.findFactoryConfigurations(ConfigurationSuppor
t.java:526)
        at org.apache.felix.scr.impl.config.ConfigurationSupport.configureComponentHolder(ConfigurationSupport
.java:124)
        at org.apache.felix.scr.impl.ComponentRegistry.registerComponentHolder(ComponentRegistry.java:421)
        at org.apache.felix.scr.impl.BundleComponentActivator.loadDescriptor(BundleComponentActivator.java:263
)
        at org.apache.felix.scr.impl.BundleComponentActivator.initialize(BundleComponentActivator.java:153)
        at org.apache.felix.scr.impl.BundleComponentActivator.<init>(BundleComponentActivator.java:115)
        at org.apache.felix.scr.impl.Activator.loadComponents(Activator.java:261)
        at org.apache.felix.scr.impl.Activator.bundleChanged(Activator.java:180)
        at org.apache.felix.framework.util.EventDispatcher.invokeBundleListenerCallback(EventDispatcher.java:8
68)
        at org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:789)
        at org.apache.felix.framework.util.EventDispatcher.fireBundleEvent(EventDispatcher.java:514)
        at org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:4403)
        at org.apache.felix.framework.Felix.startBundle(Felix.java:2092)
        at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:955)
        at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:942)
        at com.nuance.docimg.dws.xerox.devicelifecycleprovider.impl.XeroxDeviceLifecycleProvider.add(XeroxDevi
ceLifecycleProvider.java:168)
        at com.nuance.docimg.dws.core.devicelifecyclemanager.impl.DeviceLifecycleService.add(DeviceLifecycleSe
rvice.java:435)
        at com.nuance.docimg.dws.core.devicelifecyclemanager.impl.DeviceLifecycleService.add(DeviceLifecycleSe
rvice.java:465)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:601)
        at org.apache.felix.gogo.runtime.Reflective.invoke(Reflective.java:137)
        at org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:82)
        at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:477)
        at org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:403)
        at org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)
        at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)
        at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)
        at org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:89)
        at org.apache.felix.gogo.shell.Console.run(Console.java:62)
        at org.apache.felix.gogo.shell.Shell.console(Shell.java:203)
        at org.apache.felix.gogo.shell.Shell.gosh(Shell.java:128)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:601)
        at org.apache.felix.gogo.runtime.Reflective.invoke(Reflective.java:137)
        at org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:82)
        at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:477)
        at org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:403)
        at org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)
        at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)
        at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)
        at org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:89)
        at org.apache.felix.gogo.shell.Activator.run(Activator.java:75)
        at java.lang.Thread.run(Thread.java:722)
Invalid Configuration selection filter (|(service.pid=com.nuance.docimg.wedp.providers.WedpSessionComponent)(s
ervice.pid=com.nuance.docimg.wedp.providers.WedpSessionComponent|WedpInstanceTemplateImpl.XeroxECSP-10.16.2.83
)(service.pid=com.nuance.docimg.wedp.providers.WedpSessionComponent|WedpInstanceTemplateImpl.XeroxECSP-10.16.2
.83|1.0.0)(service.pid=com.nuance.docimg.wedp.providers.WedpSessionComponent|WedpInstanceTemplateImpl.XeroxECS
P-10.16.2.83|1.0.0|file:/C:/tools/apache-tomcat-7.0.39(x32)/webapps/DwsMain/WEB-INF/wedptemplate/WedpInstanceT
emplateImpl.XeroxECSP-10.16.2.83.jar))
org.apache.felix.log.LogException: org.osgi.framework.InvalidSyntaxException: Unknown operator: : (|(service.p
id=com.nuance.docimg.wedp.providers.WedpSessionComponent)(service.pid=com.nuance.docimg.wedp.providers.WedpSes
sionComponent|WedpInstanceTemplateImpl.XeroxECSP-10.16.2.83)(service.pid=com.nuance.docimg.wedp.providers.Wedp
SessionComponent|WedpInstanceTemplateImpl.XeroxECSP-10.16.2.83|1.0.0)(service.pid=com.nuance.docimg.wedp.provi
ders.WedpSessionComponent|WedpInstanceTemplateImpl.XeroxECSP-10.16.2.83|1.0.0|file:/C:/tools/apache-tomcat-7.0
.39(x32)/webapps/DwsMain/WEB-INF/wedptemplate/WedpInstanceTemplateImpl.XeroxECSP-10.16.2.83.jar))
        at org.apache.felix.framework.FilterImpl.<init>(FilterImpl.java:51)
        at org.apache.felix.framework.BundleContextImpl.createFilter(BundleContextImpl.java:132)
        at org.apache.felix.cm.impl.ConfigurationManager.listConfigurations(ConfigurationManager.java:636)
        at org.apache.felix.cm.impl.ConfigurationAdminImpl.listConfigurations(ConfigurationAdminImpl.java:169)
        at org.apache.felix.scr.impl.config.ConfigurationSupport.findConfigurations(ConfigurationSupport.java:
578)
        at org.apache.felix.scr.impl.config.ConfigurationSupport.findSingletonConfiguration(ConfigurationSuppo
rt.java:491)
        at org.apache.felix.scr.impl.config.ConfigurationSupport.configureComponentHolder(ConfigurationSupport
.java:140)
        at org.apache.felix.scr.impl.ComponentRegistry.registerComponentHolder(ComponentRegistry.java:421)
        at org.apache.felix.scr.impl.BundleComponentActivator.loadDescriptor(BundleComponentActivator.java:263
)
        at org.apache.felix.scr.impl.BundleComponentActivator.initialize(BundleComponentActivator.java:153)
        at org.apache.felix.scr.impl.BundleComponentActivator.<init>(BundleComponentActivator.java:115)
        at org.apache.felix.scr.impl.Activator.loadComponents(Activator.java:261)
        at org.apache.felix.scr.impl.Activator.bundleChanged(Activator.java:180)
        at org.apache.felix.framework.util.EventDispatcher.invokeBundleListenerCallback(EventDispatcher.java:8
68)
        at org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:789)
        at org.apache.felix.framework.util.EventDispatcher.fireBundleEvent(EventDispatcher.java:514)
        at org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:4403)
        at org.apache.felix.framework.Felix.startBundle(Felix.java:2092)
        at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:955)
        at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:942)
        at com.nuance.docimg.dws.xerox.devicelifecycleprovider.impl.XeroxDeviceLifecycleProvider.add(XeroxDevi
ceLifecycleProvider.java:168)
        at com.nuance.docimg.dws.core.devicelifecyclemanager.impl.DeviceLifecycleService.add(DeviceLifecycleSe
rvice.java:435)
        at com.nuance.docimg.dws.core.devicelifecyclemanager.impl.DeviceLifecycleService.add(DeviceLifecycleSe
rvice.java:465)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:601)
        at org.apache.felix.gogo.runtime.Reflective.invoke(Reflective.java:137)
        at org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:82)
        at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:477)
        at org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:403)
        at org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)
        at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)
        at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)
        at org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:89)
        at org.apache.felix.gogo.shell.Console.run(Console.java:62)
        at org.apache.felix.gogo.shell.Shell.console(Shell.java:203)
        at org.apache.felix.gogo.shell.Shell.gosh(Shell.java:128)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:601)
        at org.apache.felix.gogo.runtime.Reflective.invoke(Reflective.java:137)
        at org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:82)
        at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:477)
        at org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:403)
        at org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)
        at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)
        at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)
        at org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:89)
        at org.apache.felix.gogo.shell.Activator.run(Activator.java:75)
        at java.lang.Thread.run(Thread.java:722)
{log=DwsCoreImpl.DwsCoreEnvironment.37}class com.nuance.docimg.dws.core.environment.impl.DwsCoreEnvironment.ge
tTemplateInstallPath(): Gogo shell: Template found at: C:\tools\apache-tomcat-7.0.39(x32)\webapps\DwsMain\WEB-
INF\wedptemplate\WedpInstanceTemplateImpl.jar
 
 
Note that when I tried to update to the latest code I had a test failure and if I skip the unit tests it just fails due to aapche-rat licenes. I have the test failure and apache rat error below.
 
log level: 2 D=16:36:20,606 T=Thread[FelixDispatchQueue,5,main]: FrameworkEvent:
 PACKAGE REFRESHED
[org.ops4j.exec.DefaultJavaRunner] : org.ops4j.pax.logging.pax-logging-api[org.o
ps4j.pax.swissbox.extender.BundleWatcherShutdown in progress...
] : Releasing bundle [org.ops4j.pax.exam.invoker.junit]
[org.ops4j.exec.DefaultJavaRunner] : Unwrapping stream I/O.
[org.ops4j.exec.DefaultJavaRunner] : Platform has been shutdown.
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 9.575 sec
Results :
Tests in error:
  test_concurrent_injection_with_bundleContext:Felix3680_2Test.test_concurrent_i
njection_with_bundleContext:org.ops4j.pax.exam.forked.ForkedTestContainer@effaa(
org.apache.felix.scr.integration.Felix3680_2Test)
Tests run: 91, Failures: 0, Errors: 1, Skipped: 0
[WARNING] File encoding has not been set, using platform encoding Cp1252, i.e. b
uild is platform dependent!
[INFO]
[INFO] --- apache-rat-plugin:0.7:check (default) @ org.apache.felix.scr ---
[INFO] Exclude: src/main/appended-resources/**
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 7:57.548s
[INFO] Finished at: Tue May 28 16:36:23 EDT 2013
[INFO] Final Memory: 14M/457M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.7:check (defau
lt) on project org.apache.felix.scr: Too many unapproved licenses: 1 -> [Help 1]
 		 	   		  

Re: SCR 1.6.2 behaviour change - services bound in an activate method are no longer bound back to the same component instance

Posted by David Jencks <da...@yahoo.com>.
Felix DS has very very extensive logging but it uses an OSGI logging service.  So you need to install one to get any output.  For instance the DS integration tests install a simple logger.

A DS component is only one class.  You can't spread the methods into more than one class and have one component, such as the activate/deactivate in one class and the reference bind/unbind methods in another.

An exception in the activate method will prevent the component from being set up.

If I've understood your setup you have a mandatory dependency from one class.  DS will only try to create the implementation object after all the required dependencies are present.  Not having all the required dependencies is in no sense an error condition.  Even so if you have logging set up there are numerous debug level messages explaining that dependencies are missing so activation cannot proceed.

hope this helps

david jencks

On May 29, 2013, at 2:40 AM, Snorre Lothar von Gohren Edwin <sn...@gmail.com> wrote:

> Im sorry if this is not clear at all, but il try to answer these questions
> and that might help.
> As for the null object, it was a object that had not be set yet, or existed
> but not yet created. That was a silly mistake from my side, probably copy
> paste error, but the IDE didnt see anything wrong with the code.
> 
> *1) What am I trying to achieve;*
> First of all im just trying out OSGi, so basically, im trying to achieve an
> understanding of the why and how.
> But in this current question im trying to achieve a DS component that
> activate and deactivate, with the possibility to bind and unbind.
> I did solve some problems I didn't understand yesterday, and that is why I
> sent the mail.
> In the end im trying to make a Java gui which will be a container for GUIs
> that comes with the services. And it should deliver messages to the service
> frame and should get messages from the service frame.
> Basically its a control station for other services to register and they
> should be able to communicate. This is probably best done with the
> whiteboard pattern, if I have understood correctly?
> 
> *2) What did I try to do;*
> 
> 1) I tried to activate a bundle which had a simple sysout, and the objecet
> was accidentely null. This was a mistake because of a copy paste probably.
> But this stopped the code.
> 2) I also started over from scratch to try to get the service to bind. Then
> I figuered out that I had to have the implementation resolved to for
> anything to happen. Now im just curious why.
> 3)I also tried to put the bind and unbind methods in another class, a class
> that would be created from the class with the activate method. But this
> seems to cause some problems.
> 
> 
> *3) What did I *expect* to see as the result of doing (2);*
> 
> 1) I expected at least some message back from the framework on the null
> mistake, a nullpointer excetion.
> 2) As this attempt. I registered the interface but forgot the
> implementation. Its logical that the setMethod(Reference) didn't go off.
> But still im used to some kind of error message or warning.
> 3)As for the setting the bind and unbind in another class, I expected the
> bind and unbind methods to trigger, I also tried to put the bind methods
> inside the class with the activate method, and then it worked.
> 
> *4) What did I *actually* see as a result of doing (2);*
> 
> 1) I didn't get any exceptions at all, it just started my bundle like
> everything was ok. Except it was like it never ran the activate method.
> I know its silly but alot of time was used to understand why the activate
> method didn't start, at least that what I thought it didn't, but since this
> sysout of the object that was unfortunately null, it was the first line, it
> stopped without any exceptions.
> 2) Also here nothing happened, but again im used to some kind of error
> message or warning, but this was actually silly.
> 3) This one is a little more confusing, nothing happens here. I create the
> new class, but the bind(@Reference) wont trigger in this class. Its
> probably some kind of settings mistake but I havent figured it out yet.
> 
> *5) Why do I believe that what actually happened is wrong?*
> I don't think I said it was wrong but as I have mentioned a couple of
> times, im used to getting some kind of error or warning. Unresolved
> warning, nullpointer exception or something to work out from.
> But the framework didn't give me anything which was frustrating to work
> with. And the mail to that thread was basically to mention that I as a
> newbie, felt that it was some warnings missing when I figured out what the
> mistakes were.
> 
> Hopes this helps understanding my questions and inquiries.
> 
> 
> -- 
> Mvh
> Snorre Lothar von Gohren Edwin
> +47 411 611 94


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org


Re: SCR 1.6.2 behaviour change - services bound in an activate method are no longer bound back to the same component instance

Posted by Snorre Lothar von Gohren Edwin <sn...@gmail.com>.
Im sorry if this is not clear at all, but il try to answer these questions
and that might help.
As for the null object, it was a object that had not be set yet, or existed
but not yet created. That was a silly mistake from my side, probably copy
paste error, but the IDE didnt see anything wrong with the code.

*1) What am I trying to achieve;*
First of all im just trying out OSGi, so basically, im trying to achieve an
understanding of the why and how.
But in this current question im trying to achieve a DS component that
activate and deactivate, with the possibility to bind and unbind.
I did solve some problems I didn't understand yesterday, and that is why I
sent the mail.
In the end im trying to make a Java gui which will be a container for GUIs
that comes with the services. And it should deliver messages to the service
frame and should get messages from the service frame.
Basically its a control station for other services to register and they
should be able to communicate. This is probably best done with the
whiteboard pattern, if I have understood correctly?

*2) What did I try to do;*

1) I tried to activate a bundle which had a simple sysout, and the objecet
was accidentely null. This was a mistake because of a copy paste probably.
But this stopped the code.
2) I also started over from scratch to try to get the service to bind. Then
I figuered out that I had to have the implementation resolved to for
anything to happen. Now im just curious why.
3)I also tried to put the bind and unbind methods in another class, a class
that would be created from the class with the activate method. But this
seems to cause some problems.


*3) What did I *expect* to see as the result of doing (2);*

1) I expected at least some message back from the framework on the null
mistake, a nullpointer excetion.
2) As this attempt. I registered the interface but forgot the
implementation. Its logical that the setMethod(Reference) didn't go off.
But still im used to some kind of error message or warning.
3)As for the setting the bind and unbind in another class, I expected the
bind and unbind methods to trigger, I also tried to put the bind methods
inside the class with the activate method, and then it worked.

*4) What did I *actually* see as a result of doing (2);*

1) I didn't get any exceptions at all, it just started my bundle like
everything was ok. Except it was like it never ran the activate method.
I know its silly but alot of time was used to understand why the activate
method didn't start, at least that what I thought it didn't, but since this
sysout of the object that was unfortunately null, it was the first line, it
stopped without any exceptions.
2) Also here nothing happened, but again im used to some kind of error
message or warning, but this was actually silly.
3) This one is a little more confusing, nothing happens here. I create the
new class, but the bind(@Reference) wont trigger in this class. Its
probably some kind of settings mistake but I havent figured it out yet.

*5) Why do I believe that what actually happened is wrong?*
I don't think I said it was wrong but as I have mentioned a couple of
times, im used to getting some kind of error or warning. Unresolved
warning, nullpointer exception or something to work out from.
But the framework didn't give me anything which was frustrating to work
with. And the mail to that thread was basically to mention that I as a
newbie, felt that it was some warnings missing when I figured out what the
mistakes were.

Hopes this helps understanding my questions and inquiries.


-- 
Mvh
Snorre Lothar von Gohren Edwin
+47 411 611 94

Re: SCR 1.6.2 behaviour change - services bound in an activate method are no longer bound back to the same component instance

Posted by Neil Bartlett <nj...@gmail.com>.
Hi Snorre,

No I'm sorry, but none of this is clear at all! For example you keep
talking about "doing something to a null object". What do you mean?? What
is a null object? Where did the null object come from, what is the
"something" you are trying to do? Then you said that "the code stops". What
code?? In what way does it stop... does it throw an exception? Do you see
some kind of error... or a deadlock??

So, please answer the following questions as clearly and specifically as
possible, without assuming that we already know anything about what your
assignment is:

1) What am I trying to achieve;
2) What did I try to do;
3) What did I *expect* to see as the result of doing (2);
4) What did I *actually* see as a result of doing (2);
5) Why do I believe that what actually happened is wrong?

With regard to your reference method not being called... how is this an
error? You have defined a mandatory reference to a service, so if that
service does not exist then your component should not be activated. If the
"lableupdated.Api" service becomes available later then you component will
be activated at that time. So this is not an error, it is correct
behaviour. If you expected to see the component activated, then you can use
the scr:list and scr:info commands from the Gogo shell to diagnose.

Regards,
Neil


On Tue, May 28, 2013 at 10:50 PM, Snorre Lothar von Gohren Edwin <
snorre.edwin@gmail.com> wrote:

> Ok il try again. Because its actually really basic and simple.
> https://github.com/Snorlock/prosjektoppgavekode/tree/troubles
>
> No need to clone, I can explain it here. A disclaimer, this is not business
> project, its for my assignment and the way im learning OSGi, so just ignore
> stupid variables and stupid stuff for now ^^
>
> If you take a look at the repo provided above. Focus on roadstation package
> and labelupdater packages. This class is inside roadstation:
> http://goo.gl/Qp85a
> Right now all that is connected is the *roadstation*, *lableupdater *and *
> labelupdater.impl.* The labelupdater provides a service api. And
> labelupdate.impl is the service implementation.
>
> Roadsatation Activatorzzz is the DS component im trying to play around
> with. First problem is that if I don't resolve my labelupdater.impl, the
> @Reference method in Activatorzzz(see the refrences class link) is not
> triggered, and the bundle goes into active. Shouldn't there be some sort of
> logging message or callback telling that since there is no implementations,
> this @Reference method wont be triggered.
>
> Second, doing something to a null object, that might be a mistake one have
> done somewhere in the code, the code stops. I know the method is triggered
> because it prints out my text before the null object, but not after. Then I
> refere to the activate method.
>
> I know this is really newbie stuff but for some reason i feel that its
> important with callbacks when something that is wrong goes wrong.
> But is this clearer now?
>
> And I feel that I almost have to apologize for bringing this kind of stuff
> to the mailing list, but all i have of source of information when im really
> stuck is this list and the #karaf irc channel. For some reason I dont use
> stackoverflow for OSGi related questions. Feel that it might take to long
> of a time to get a respons.
>
>
>
>
> On Tue, May 28, 2013 at 11:26 PM, David Jencks <david_jencks@yahoo.com
> >wrote:
>
> > Hi Snorre,
> >
> > I don't understand what you are asking very well.  What are you trying to
> > do with a null object and what does this have to do with DS?  What code
> > stops running?  How do you know it's stopped rather than never started?
> >
> > What do you mean by a service that is registered without an
> > implementation?  You've registered a ServiceFactory?  What is the
> > setService function?
> >
> > I think you posted a link to a github repo but I haven't had time to
> clone
> > it and investigate.  Could you provide more details in your emails
> without
> > duplicating the project?  For instance show how many bundles you have set
> > up, which DS components are in which bundles, how you want to use the DS
> > services, and something about the DS components.
> >
> > One possibility that might explain what I think you are describing
> below--
> > it's hard to tell -- is that your DS component registers a service but is
> > not marked immediate.  Then the service will be registered right away but
> > the implementation object will only be created when the service is
> > requested from the service reference.
> >
> > thanks
> > david jencks
> >
> > On May 28, 2013, at 1:39 PM, Snorre Lothar von Gohren Edwin <
> > snorre.edwin@gmail.com> wrote:
> >
> > > I would like to add a question to this thread. For some reason when im
> > > using DS and im trying to do something with a null object. I dont get
> any
> > > respons at all. The code just stops running, and runs everything else.
> > > Also, if I have a service that is registered, but without an
> > > implementation, the setService function just wont run and it does not
> > > provide any feedback. Is it suppose to be like this, it does waste a
> lot
> > of
> > > time for new developers to debug this stuff.
> > >
> > > For example:
> > >
> > > @Activate
> > > public void activate(ComponentContext ctx) {
> > > System.out.println(context.getBundle().getSymbolicName());
> > > this.context = ctx.getBundleContext();
> > > System.out.println("YOlllo!");
> > > run();
> > > }
> > >
> > >
> > > This context is null, yes I know its wrong but this is just a display
> > > method for you guys to see. Running this provides nothing at all. The
> > > bundle dont do anything but still has state as active.
> > > Shouldnt this provide some sort of warning?
> > >
> > > Maybe there is something I have not gotten to in the DS spesifications
> > but
> > > just a headsup for use newbies that is trying to learn OSGi and might
> one
> > > day convince other to use it.
> > >
> > >
> > >
> > >
> > > On Tue, May 28, 2013 at 10:14 PM, David Jencks <david_jencks@yahoo.com
> > >wrote:
> > >
> > >> I'm currently not aware of any problems I want to fix in DS although
> I'd
> > >> like to write some tests for the new location binding and targeted PID
> > >> functionality… so I might be interested in a release soon.  There have
> > been
> > >> a lot of changes so I'd rather appreciate it if you could try out the
> > >> current code.
> > >>
> > >> My last attempt to upload a DS snapshot didn't work, can anyone else
> > have
> > >> a try?
> > >>
> > >> thanks
> > >> david jencks
> > >>
> > >> On May 28, 2013, at 8:01 AM, Robert Munteanu <ro...@lmn.ro> wrote:
> > >>
> > >>> On Tue, May 28, 2013 at 5:55 PM, Felix Meschberger <
> fmeschbe@adobe.com
> > >
> > >> wrote:
> > >>>> HI Robert
> > >>>>
> > >>>> As I noted in your issue (SLING-2876) this is fixed post-1.6.2 as
> per
> > >> FELIX-3754. It has been a timing issue handling the activator and the
> > bind
> > >> methods.
> > >>>>
> > >>>> Hope this helps.
> > >>>
> > >>> Hi Felix,
> > >>>
> > >>> Thanks for the pointer, I saw the issue comment after I posted this
> > >>> mail. I'll just revert to a SCR 1.6.0 until 1.8.0 is out.
> > >>>
> > >>> Robert
> > >>>
> > >>>>
> > >>>> Regards
> > >>>> Felix
> > >>>>
> > >>>> Am 28.05.2013 um 16:52 schrieb Robert Munteanu:
> > >>>>
> > >>>>> Hi,
> > >>>>>
> > >>>>> I've noticed a behaviour change when upgrading from SCR 1.6.0 to
> > 1.6.2
> > >> .
> > >>>>>
> > >>>>> In the Apache Sling project we have a component which binds service
> > >>>>> references in its own activate method, and expects them to be bound
> > to
> > >>>>> itself later on ( see [0], near the end of the activate method ).
> > >>>>>
> > >>>>> With SCR 1.6.0, these components are bound. With 1.6.2 they are not
> > >> bound.
> > >>>>>
> > >>>>> I found nothing relevant to this edge case in the OSGi Declarative
> > >>>>> Services spec, so my question is : is this change intended or
> > >>>>> accidental?
> > >>>>>
> > >>>>> Thanks,
> > >>>>>
> > >>>>> Robert
> > >>>>>
> > >>>>>
> > >>>>> [0]:
> > >>
> >
> http://svn.apache.org/repos/asf/sling/trunk/bundles/servlets/post/src/main/java/org/apache/sling/servlets/post/impl/SlingPostServlet.java
> > >>>>>
> > >>>>>
> ---------------------------------------------------------------------
> > >>>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> > >>>>> For additional commands, e-mail: users-help@felix.apache.org
> > >>>>>
> > >>>>
> > >>>>
> > >>>>
> ---------------------------------------------------------------------
> > >>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> > >>>> For additional commands, e-mail: users-help@felix.apache.org
> > >>>>
> > >>>
> > >>>
> > >>>
> > >>> --
> > >>> Sent from my (old) computer
> > >>>
> > >>> ---------------------------------------------------------------------
> > >>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> > >>> For additional commands, e-mail: users-help@felix.apache.org
> > >>>
> > >>
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> > >> For additional commands, e-mail: users-help@felix.apache.org
> > >>
> > >>
> > >
> > >
> > > --
> > > Mvh
> > > Snorre Lothar von Gohren Edwin
> > > +47 411 611 94
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> > For additional commands, e-mail: users-help@felix.apache.org
> >
> >
>
>
> --
> Mvh
> Snorre Lothar von Gohren Edwin
> +47 411 611 94
>

Re: SCR 1.6.2 behaviour change - services bound in an activate method are no longer bound back to the same component instance

Posted by Snorre Lothar von Gohren Edwin <sn...@gmail.com>.
Ok il try again. Because its actually really basic and simple.
https://github.com/Snorlock/prosjektoppgavekode/tree/troubles

No need to clone, I can explain it here. A disclaimer, this is not business
project, its for my assignment and the way im learning OSGi, so just ignore
stupid variables and stupid stuff for now ^^

If you take a look at the repo provided above. Focus on roadstation package
and labelupdater packages. This class is inside roadstation:
http://goo.gl/Qp85a
Right now all that is connected is the *roadstation*, *lableupdater *and *
labelupdater.impl.* The labelupdater provides a service api. And
labelupdate.impl is the service implementation.

Roadsatation Activatorzzz is the DS component im trying to play around
with. First problem is that if I don't resolve my labelupdater.impl, the
@Reference method in Activatorzzz(see the refrences class link) is not
triggered, and the bundle goes into active. Shouldn't there be some sort of
logging message or callback telling that since there is no implementations,
this @Reference method wont be triggered.

Second, doing something to a null object, that might be a mistake one have
done somewhere in the code, the code stops. I know the method is triggered
because it prints out my text before the null object, but not after. Then I
refere to the activate method.

I know this is really newbie stuff but for some reason i feel that its
important with callbacks when something that is wrong goes wrong.
But is this clearer now?

And I feel that I almost have to apologize for bringing this kind of stuff
to the mailing list, but all i have of source of information when im really
stuck is this list and the #karaf irc channel. For some reason I dont use
stackoverflow for OSGi related questions. Feel that it might take to long
of a time to get a respons.




On Tue, May 28, 2013 at 11:26 PM, David Jencks <da...@yahoo.com>wrote:

> Hi Snorre,
>
> I don't understand what you are asking very well.  What are you trying to
> do with a null object and what does this have to do with DS?  What code
> stops running?  How do you know it's stopped rather than never started?
>
> What do you mean by a service that is registered without an
> implementation?  You've registered a ServiceFactory?  What is the
> setService function?
>
> I think you posted a link to a github repo but I haven't had time to clone
> it and investigate.  Could you provide more details in your emails without
> duplicating the project?  For instance show how many bundles you have set
> up, which DS components are in which bundles, how you want to use the DS
> services, and something about the DS components.
>
> One possibility that might explain what I think you are describing below--
> it's hard to tell -- is that your DS component registers a service but is
> not marked immediate.  Then the service will be registered right away but
> the implementation object will only be created when the service is
> requested from the service reference.
>
> thanks
> david jencks
>
> On May 28, 2013, at 1:39 PM, Snorre Lothar von Gohren Edwin <
> snorre.edwin@gmail.com> wrote:
>
> > I would like to add a question to this thread. For some reason when im
> > using DS and im trying to do something with a null object. I dont get any
> > respons at all. The code just stops running, and runs everything else.
> > Also, if I have a service that is registered, but without an
> > implementation, the setService function just wont run and it does not
> > provide any feedback. Is it suppose to be like this, it does waste a lot
> of
> > time for new developers to debug this stuff.
> >
> > For example:
> >
> > @Activate
> > public void activate(ComponentContext ctx) {
> > System.out.println(context.getBundle().getSymbolicName());
> > this.context = ctx.getBundleContext();
> > System.out.println("YOlllo!");
> > run();
> > }
> >
> >
> > This context is null, yes I know its wrong but this is just a display
> > method for you guys to see. Running this provides nothing at all. The
> > bundle dont do anything but still has state as active.
> > Shouldnt this provide some sort of warning?
> >
> > Maybe there is something I have not gotten to in the DS spesifications
> but
> > just a headsup for use newbies that is trying to learn OSGi and might one
> > day convince other to use it.
> >
> >
> >
> >
> > On Tue, May 28, 2013 at 10:14 PM, David Jencks <david_jencks@yahoo.com
> >wrote:
> >
> >> I'm currently not aware of any problems I want to fix in DS although I'd
> >> like to write some tests for the new location binding and targeted PID
> >> functionality… so I might be interested in a release soon.  There have
> been
> >> a lot of changes so I'd rather appreciate it if you could try out the
> >> current code.
> >>
> >> My last attempt to upload a DS snapshot didn't work, can anyone else
> have
> >> a try?
> >>
> >> thanks
> >> david jencks
> >>
> >> On May 28, 2013, at 8:01 AM, Robert Munteanu <ro...@lmn.ro> wrote:
> >>
> >>> On Tue, May 28, 2013 at 5:55 PM, Felix Meschberger <fmeschbe@adobe.com
> >
> >> wrote:
> >>>> HI Robert
> >>>>
> >>>> As I noted in your issue (SLING-2876) this is fixed post-1.6.2 as per
> >> FELIX-3754. It has been a timing issue handling the activator and the
> bind
> >> methods.
> >>>>
> >>>> Hope this helps.
> >>>
> >>> Hi Felix,
> >>>
> >>> Thanks for the pointer, I saw the issue comment after I posted this
> >>> mail. I'll just revert to a SCR 1.6.0 until 1.8.0 is out.
> >>>
> >>> Robert
> >>>
> >>>>
> >>>> Regards
> >>>> Felix
> >>>>
> >>>> Am 28.05.2013 um 16:52 schrieb Robert Munteanu:
> >>>>
> >>>>> Hi,
> >>>>>
> >>>>> I've noticed a behaviour change when upgrading from SCR 1.6.0 to
> 1.6.2
> >> .
> >>>>>
> >>>>> In the Apache Sling project we have a component which binds service
> >>>>> references in its own activate method, and expects them to be bound
> to
> >>>>> itself later on ( see [0], near the end of the activate method ).
> >>>>>
> >>>>> With SCR 1.6.0, these components are bound. With 1.6.2 they are not
> >> bound.
> >>>>>
> >>>>> I found nothing relevant to this edge case in the OSGi Declarative
> >>>>> Services spec, so my question is : is this change intended or
> >>>>> accidental?
> >>>>>
> >>>>> Thanks,
> >>>>>
> >>>>> Robert
> >>>>>
> >>>>>
> >>>>> [0]:
> >>
> http://svn.apache.org/repos/asf/sling/trunk/bundles/servlets/post/src/main/java/org/apache/sling/servlets/post/impl/SlingPostServlet.java
> >>>>>
> >>>>> ---------------------------------------------------------------------
> >>>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> >>>>> For additional commands, e-mail: users-help@felix.apache.org
> >>>>>
> >>>>
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> >>>> For additional commands, e-mail: users-help@felix.apache.org
> >>>>
> >>>
> >>>
> >>>
> >>> --
> >>> Sent from my (old) computer
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> >>> For additional commands, e-mail: users-help@felix.apache.org
> >>>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> >> For additional commands, e-mail: users-help@felix.apache.org
> >>
> >>
> >
> >
> > --
> > Mvh
> > Snorre Lothar von Gohren Edwin
> > +47 411 611 94
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
>


-- 
Mvh
Snorre Lothar von Gohren Edwin
+47 411 611 94

Re: SCR 1.6.2 behaviour change - services bound in an activate method are no longer bound back to the same component instance

Posted by David Jencks <da...@yahoo.com>.
Hi Snorre,

I don't understand what you are asking very well.  What are you trying to do with a null object and what does this have to do with DS?  What code stops running?  How do you know it's stopped rather than never started?

What do you mean by a service that is registered without an implementation?  You've registered a ServiceFactory?  What is the setService function?

I think you posted a link to a github repo but I haven't had time to clone it and investigate.  Could you provide more details in your emails without duplicating the project?  For instance show how many bundles you have set up, which DS components are in which bundles, how you want to use the DS services, and something about the DS components.

One possibility that might explain what I think you are describing below-- it's hard to tell -- is that your DS component registers a service but is not marked immediate.  Then the service will be registered right away but the implementation object will only be created when the service is requested from the service reference.

thanks
david jencks

On May 28, 2013, at 1:39 PM, Snorre Lothar von Gohren Edwin <sn...@gmail.com> wrote:

> I would like to add a question to this thread. For some reason when im
> using DS and im trying to do something with a null object. I dont get any
> respons at all. The code just stops running, and runs everything else.
> Also, if I have a service that is registered, but without an
> implementation, the setService function just wont run and it does not
> provide any feedback. Is it suppose to be like this, it does waste a lot of
> time for new developers to debug this stuff.
> 
> For example:
> 
> @Activate
> public void activate(ComponentContext ctx) {
> System.out.println(context.getBundle().getSymbolicName());
> this.context = ctx.getBundleContext();
> System.out.println("YOlllo!");
> run();
> }
> 
> 
> This context is null, yes I know its wrong but this is just a display
> method for you guys to see. Running this provides nothing at all. The
> bundle dont do anything but still has state as active.
> Shouldnt this provide some sort of warning?
> 
> Maybe there is something I have not gotten to in the DS spesifications but
> just a headsup for use newbies that is trying to learn OSGi and might one
> day convince other to use it.
> 
> 
> 
> 
> On Tue, May 28, 2013 at 10:14 PM, David Jencks <da...@yahoo.com>wrote:
> 
>> I'm currently not aware of any problems I want to fix in DS although I'd
>> like to write some tests for the new location binding and targeted PID
>> functionality… so I might be interested in a release soon.  There have been
>> a lot of changes so I'd rather appreciate it if you could try out the
>> current code.
>> 
>> My last attempt to upload a DS snapshot didn't work, can anyone else have
>> a try?
>> 
>> thanks
>> david jencks
>> 
>> On May 28, 2013, at 8:01 AM, Robert Munteanu <ro...@lmn.ro> wrote:
>> 
>>> On Tue, May 28, 2013 at 5:55 PM, Felix Meschberger <fm...@adobe.com>
>> wrote:
>>>> HI Robert
>>>> 
>>>> As I noted in your issue (SLING-2876) this is fixed post-1.6.2 as per
>> FELIX-3754. It has been a timing issue handling the activator and the bind
>> methods.
>>>> 
>>>> Hope this helps.
>>> 
>>> Hi Felix,
>>> 
>>> Thanks for the pointer, I saw the issue comment after I posted this
>>> mail. I'll just revert to a SCR 1.6.0 until 1.8.0 is out.
>>> 
>>> Robert
>>> 
>>>> 
>>>> Regards
>>>> Felix
>>>> 
>>>> Am 28.05.2013 um 16:52 schrieb Robert Munteanu:
>>>> 
>>>>> Hi,
>>>>> 
>>>>> I've noticed a behaviour change when upgrading from SCR 1.6.0 to 1.6.2
>> .
>>>>> 
>>>>> In the Apache Sling project we have a component which binds service
>>>>> references in its own activate method, and expects them to be bound to
>>>>> itself later on ( see [0], near the end of the activate method ).
>>>>> 
>>>>> With SCR 1.6.0, these components are bound. With 1.6.2 they are not
>> bound.
>>>>> 
>>>>> I found nothing relevant to this edge case in the OSGi Declarative
>>>>> Services spec, so my question is : is this change intended or
>>>>> accidental?
>>>>> 
>>>>> Thanks,
>>>>> 
>>>>> Robert
>>>>> 
>>>>> 
>>>>> [0]:
>> http://svn.apache.org/repos/asf/sling/trunk/bundles/servlets/post/src/main/java/org/apache/sling/servlets/post/impl/SlingPostServlet.java
>>>>> 
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>> 
>>>> 
>>>> 
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>> 
>>> 
>>> 
>>> 
>>> --
>>> Sent from my (old) computer
>>> 
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>> For additional commands, e-mail: users-help@felix.apache.org
>>> 
>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>> For additional commands, e-mail: users-help@felix.apache.org
>> 
>> 
> 
> 
> -- 
> Mvh
> Snorre Lothar von Gohren Edwin
> +47 411 611 94


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org


Re: SCR 1.6.2 behaviour change - services bound in an activate method are no longer bound back to the same component instance

Posted by Snorre Lothar von Gohren Edwin <sn...@gmail.com>.
I would like to add a question to this thread. For some reason when im
using DS and im trying to do something with a null object. I dont get any
respons at all. The code just stops running, and runs everything else.
Also, if I have a service that is registered, but without an
implementation, the setService function just wont run and it does not
provide any feedback. Is it suppose to be like this, it does waste a lot of
time for new developers to debug this stuff.

For example:

@Activate
public void activate(ComponentContext ctx) {
 System.out.println(context.getBundle().getSymbolicName());
this.context = ctx.getBundleContext();
System.out.println("YOlllo!");
 run();
 }


This context is null, yes I know its wrong but this is just a display
method for you guys to see. Running this provides nothing at all. The
bundle dont do anything but still has state as active.
Shouldnt this provide some sort of warning?

Maybe there is something I have not gotten to in the DS spesifications but
just a headsup for use newbies that is trying to learn OSGi and might one
day convince other to use it.




On Tue, May 28, 2013 at 10:14 PM, David Jencks <da...@yahoo.com>wrote:

> I'm currently not aware of any problems I want to fix in DS although I'd
> like to write some tests for the new location binding and targeted PID
> functionality… so I might be interested in a release soon.  There have been
> a lot of changes so I'd rather appreciate it if you could try out the
> current code.
>
> My last attempt to upload a DS snapshot didn't work, can anyone else have
> a try?
>
> thanks
> david jencks
>
> On May 28, 2013, at 8:01 AM, Robert Munteanu <ro...@lmn.ro> wrote:
>
> > On Tue, May 28, 2013 at 5:55 PM, Felix Meschberger <fm...@adobe.com>
> wrote:
> >> HI Robert
> >>
> >> As I noted in your issue (SLING-2876) this is fixed post-1.6.2 as per
> FELIX-3754. It has been a timing issue handling the activator and the bind
> methods.
> >>
> >> Hope this helps.
> >
> > Hi Felix,
> >
> > Thanks for the pointer, I saw the issue comment after I posted this
> > mail. I'll just revert to a SCR 1.6.0 until 1.8.0 is out.
> >
> > Robert
> >
> >>
> >> Regards
> >> Felix
> >>
> >> Am 28.05.2013 um 16:52 schrieb Robert Munteanu:
> >>
> >>> Hi,
> >>>
> >>> I've noticed a behaviour change when upgrading from SCR 1.6.0 to 1.6.2
> .
> >>>
> >>> In the Apache Sling project we have a component which binds service
> >>> references in its own activate method, and expects them to be bound to
> >>> itself later on ( see [0], near the end of the activate method ).
> >>>
> >>> With SCR 1.6.0, these components are bound. With 1.6.2 they are not
> bound.
> >>>
> >>> I found nothing relevant to this edge case in the OSGi Declarative
> >>> Services spec, so my question is : is this change intended or
> >>> accidental?
> >>>
> >>> Thanks,
> >>>
> >>> Robert
> >>>
> >>>
> >>> [0]:
> http://svn.apache.org/repos/asf/sling/trunk/bundles/servlets/post/src/main/java/org/apache/sling/servlets/post/impl/SlingPostServlet.java
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> >>> For additional commands, e-mail: users-help@felix.apache.org
> >>>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> >> For additional commands, e-mail: users-help@felix.apache.org
> >>
> >
> >
> >
> > --
> > Sent from my (old) computer
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> > For additional commands, e-mail: users-help@felix.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
>


-- 
Mvh
Snorre Lothar von Gohren Edwin
+47 411 611 94

Re: SCR 1.6.2 behaviour change - services bound in an activate method are no longer bound back to the same component instance

Posted by David Jencks <da...@yahoo.com>.
I'm currently not aware of any problems I want to fix in DS although I'd like to write some tests for the new location binding and targeted PID functionality… so I might be interested in a release soon.  There have been a lot of changes so I'd rather appreciate it if you could try out the current code.

My last attempt to upload a DS snapshot didn't work, can anyone else have a try?

thanks
david jencks

On May 28, 2013, at 8:01 AM, Robert Munteanu <ro...@lmn.ro> wrote:

> On Tue, May 28, 2013 at 5:55 PM, Felix Meschberger <fm...@adobe.com> wrote:
>> HI Robert
>> 
>> As I noted in your issue (SLING-2876) this is fixed post-1.6.2 as per FELIX-3754. It has been a timing issue handling the activator and the bind methods.
>> 
>> Hope this helps.
> 
> Hi Felix,
> 
> Thanks for the pointer, I saw the issue comment after I posted this
> mail. I'll just revert to a SCR 1.6.0 until 1.8.0 is out.
> 
> Robert
> 
>> 
>> Regards
>> Felix
>> 
>> Am 28.05.2013 um 16:52 schrieb Robert Munteanu:
>> 
>>> Hi,
>>> 
>>> I've noticed a behaviour change when upgrading from SCR 1.6.0 to 1.6.2 .
>>> 
>>> In the Apache Sling project we have a component which binds service
>>> references in its own activate method, and expects them to be bound to
>>> itself later on ( see [0], near the end of the activate method ).
>>> 
>>> With SCR 1.6.0, these components are bound. With 1.6.2 they are not bound.
>>> 
>>> I found nothing relevant to this edge case in the OSGi Declarative
>>> Services spec, so my question is : is this change intended or
>>> accidental?
>>> 
>>> Thanks,
>>> 
>>> Robert
>>> 
>>> 
>>> [0]: http://svn.apache.org/repos/asf/sling/trunk/bundles/servlets/post/src/main/java/org/apache/sling/servlets/post/impl/SlingPostServlet.java
>>> 
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>> For additional commands, e-mail: users-help@felix.apache.org
>>> 
>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>> For additional commands, e-mail: users-help@felix.apache.org
>> 
> 
> 
> 
> --
> Sent from my (old) computer
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org


Re: SCR 1.6.2 behaviour change - services bound in an activate method are no longer bound back to the same component instance

Posted by Robert Munteanu <ro...@lmn.ro>.
On Tue, May 28, 2013 at 5:55 PM, Felix Meschberger <fm...@adobe.com> wrote:
> HI Robert
>
> As I noted in your issue (SLING-2876) this is fixed post-1.6.2 as per FELIX-3754. It has been a timing issue handling the activator and the bind methods.
>
> Hope this helps.

Hi Felix,

Thanks for the pointer, I saw the issue comment after I posted this
mail. I'll just revert to a SCR 1.6.0 until 1.8.0 is out.

Robert

>
> Regards
> Felix
>
> Am 28.05.2013 um 16:52 schrieb Robert Munteanu:
>
>> Hi,
>>
>> I've noticed a behaviour change when upgrading from SCR 1.6.0 to 1.6.2 .
>>
>> In the Apache Sling project we have a component which binds service
>> references in its own activate method, and expects them to be bound to
>> itself later on ( see [0], near the end of the activate method ).
>>
>> With SCR 1.6.0, these components are bound. With 1.6.2 they are not bound.
>>
>> I found nothing relevant to this edge case in the OSGi Declarative
>> Services spec, so my question is : is this change intended or
>> accidental?
>>
>> Thanks,
>>
>> Robert
>>
>>
>> [0]: http://svn.apache.org/repos/asf/sling/trunk/bundles/servlets/post/src/main/java/org/apache/sling/servlets/post/impl/SlingPostServlet.java
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>> For additional commands, e-mail: users-help@felix.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>



--
Sent from my (old) computer

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org


Re: SCR 1.6.2 behaviour change - services bound in an activate method are no longer bound back to the same component instance

Posted by Felix Meschberger <fm...@adobe.com>.
HI Robert

As I noted in your issue (SLING-2876) this is fixed post-1.6.2 as per FELIX-3754. It has been a timing issue handling the activator and the bind methods.

Hope this helps.

Regards
Felix

Am 28.05.2013 um 16:52 schrieb Robert Munteanu:

> Hi,
> 
> I've noticed a behaviour change when upgrading from SCR 1.6.0 to 1.6.2 .
> 
> In the Apache Sling project we have a component which binds service
> references in its own activate method, and expects them to be bound to
> itself later on ( see [0], near the end of the activate method ).
> 
> With SCR 1.6.0, these components are bound. With 1.6.2 they are not bound.
> 
> I found nothing relevant to this edge case in the OSGi Declarative
> Services spec, so my question is : is this change intended or
> accidental?
> 
> Thanks,
> 
> Robert
> 
> 
> [0]: http://svn.apache.org/repos/asf/sling/trunk/bundles/servlets/post/src/main/java/org/apache/sling/servlets/post/impl/SlingPostServlet.java
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org