Re: Framework compilation problems

2014-11-12 Thread David Bosschaert
Hi Pierre, I don't see your attachment with the errors. Did you forget to attach it? Cheers, David On 12 November 2014 13:49, Pierre De Rop wrote: > Hello everyone; > > I would like to test the patch provided by Felix for the FELIX-4692 issue > ("Improve Service access time"). > But before app

Re: Make DependencyManager API more fluent?

2014-11-12 Thread Marcel Offermans
Hello Pierre, > On 12 Nov 2014, at 9:13 am, Pierre De Rop wrote: > > Regarding your suggestion, adding specific builder classes could also be an > interesting way to go. > I would even consider to make some specific API bundles, like: > > org.apache.felix.dependencymanager -> the current 4.0 AP

Re: Make DependencyManager API more fluent?

2014-11-12 Thread Marcel Offermans
Hello Christian, > On 11 Nov 2014, at 9:22 am, Christian Schneider > wrote: > > About auto adding. How about this: > Inside component() we add the component to a separate list of pending > components in dependency manager. > Then after init we call a method in the manager to finally add all pe

Re: Make DependencyManager API more fluent?

2014-11-12 Thread Marcel Offermans
Hey Paul, > On 11 Nov 2014, at 8:55 am, Paul Bakker wrote: > > One thing to consider is that although DM 4 is a major version bump, it so > far seems to be very close to a drop-in replacement of DM 3. Changing the > API itself would break all existing code. This is technically ok for a > major v

Re: Make DependencyManager API more fluent?

2014-11-12 Thread Marcel Offermans
Hey all, > On 11 Nov 2014, at 0:39 am, Pierre De Rop wrote: > > The improvements you are proposing would require a major version bump since > it's an incompatible API change. But I personally like what you are > suggesting, and I could quickly do it in the upcoming Dependency Manager > 4.0.0, wh

Framework compilation problems

2014-11-12 Thread Pierre De Rop
Hello everyone; I would like to test the patch provided by Felix for the FELIX-4692 issue ("Improve Service access time"). But before applying the patch provided by Felix, I just can't compile the framework (the tests does not seem to compile): I'm on a linux fc19, uname -a = Linux nx0012 3.14.22

[jira] [Updated] (FELIX-4622) Regression: SCR spec version detection incorrect for activate method

2014-11-12 Thread Carsten Ziegeler (JIRA)
[ https://issues.apache.org/jira/browse/FELIX-4622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated FELIX-4622: Assignee: (was: Carsten Ziegeler) > Regression: SCR spec version detection incorrect for

[jira] [Created] (FELIX-4693) When exception is thrown in "onArrival" method of iPojo white board pattern handler, related iPojo instance seems to be dead

2014-11-12 Thread Olivier Bigard (JIRA)
Olivier Bigard created FELIX-4693: - Summary: When exception is thrown in "onArrival" method of iPojo white board pattern handler, related iPojo instance seems to be dead Key: FELIX-4693 URL: https://issues.apache.

Re: Improve Service Access (FELIX-4692)

2014-11-12 Thread Richard S. Hall
On 11/12/14 09:17 , Felix Meschberger wrote: Hi I have created a patch to improve the Service Access time. With this patch applied I measure 4-5 times faster access to the service registry in our application which in general access services simply by its name and almost never uses a filter.

[jira] [Commented] (FELIX-4692) Improve Service access time

2014-11-12 Thread Richard S. Hall (JIRA)
[ https://issues.apache.org/jira/browse/FELIX-4692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14208081#comment-14208081 ] Richard S. Hall commented on FELIX-4692: Did you investigate whether or not there

Improve Service Access (FELIX-4692)

2014-11-12 Thread Felix Meschberger
Hi I have created a patch to improve the Service Access time. With this patch applied I measure 4-5 times faster access to the service registry in our application which in general access services simply by its name and almost never uses a filter. I expect that this patch also significantly imp

[jira] [Updated] (FELIX-4692) Improve Service access time

2014-11-12 Thread Felix Meschberger (JIRA)
[ https://issues.apache.org/jira/browse/FELIX-4692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated FELIX-4692: - Attachment: FELIX-4692.diff Patch with the proposed change. > Improve Service access time

[jira] [Created] (FELIX-4692) Improve Service access time

2014-11-12 Thread Felix Meschberger (JIRA)
Felix Meschberger created FELIX-4692: Summary: Improve Service access time Key: FELIX-4692 URL: https://issues.apache.org/jira/browse/FELIX-4692 Project: Felix Issue Type: Improvement

[jira] [Updated] (FELIX-4691) Empty string value for property causes build failure

2014-11-12 Thread JIRA
[ https://issues.apache.org/jira/browse/FELIX-4691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Åsberg updated FELIX-4691: - Attachment: servicepropertytest.zip Minimal Maven sample project illustrating the failure. See it

[jira] [Created] (FELIX-4691) Empty string value for property causes build failure

2014-11-12 Thread JIRA
Mikael Åsberg created FELIX-4691: Summary: Empty string value for property causes build failure Key: FELIX-4691 URL: https://issues.apache.org/jira/browse/FELIX-4691 Project: Felix Issue Type

[jira] [Resolved] (FELIX-4413) Update maven-scr-plugin to use standard OSGi annotations

2014-11-12 Thread Carsten Ziegeler (JIRA)
[ https://issues.apache.org/jira/browse/FELIX-4413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-4413. - Resolution: Fixed This is documented now > Update maven-scr-plugin to use standard OSGi a

[jira] [Updated] (FELIX-4413) Update maven-scr-plugin to use standard OSGi annotations

2014-11-12 Thread Carsten Ziegeler (JIRA)
[ https://issues.apache.org/jira/browse/FELIX-4413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated FELIX-4413: Fix Version/s: maven-scr-plugin 1.20.0 > Update maven-scr-plugin to use standard OSGi annota

[jira] [Updated] (FELIX-4622) Regression: SCR spec version detection incorrect for activate method

2014-11-12 Thread Carsten Ziegeler (JIRA)
[ https://issues.apache.org/jira/browse/FELIX-4622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated FELIX-4622: Fix Version/s: maven-scr-plugin 1.21.0 > Regression: SCR spec version detection incorrect fo

[jira] [Assigned] (FELIX-4622) Regression: SCR spec version detection incorrect for activate method

2014-11-12 Thread Carsten Ziegeler (JIRA)
[ https://issues.apache.org/jira/browse/FELIX-4622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned FELIX-4622: --- Assignee: Carsten Ziegeler > Regression: SCR spec version detection incorrect for act

Re: Make DependencyManager API more fluent?

2014-11-12 Thread Christian Schneider
Sounds good to me. For me it is not time critical so I can wait till you signal me that the code is in good shape. Christian On 12.11.2014 09:14, Pierre De Rop wrote: Hello Christian, We could indeed deprecate all the setters methods, and introduce your proposed builder methods. And I do agr

Re: Make DependencyManager API more fluent?

2014-11-12 Thread Paul Bakker
Hi Pierre, Don't worry, I don't think it's a problem at all if some things changed. It's a huge new release after all! I was only suggesting that we shouldn't get rid of the component registration API completely in favour of a better API. For the methods that don't longer exist etc. I don't see mu

Re: Make DependencyManager API more fluent?

2014-11-12 Thread Pierre De Rop
Hello Christian, We could indeed deprecate all the setters methods, and introduce your proposed builder methods. And I do agree that we could also manage to let the new DependencyActivatorBase.component() method maintain the list of created components, and we could then auto-add all the created co

Re: Make DependencyManager API more fluent?

2014-11-12 Thread Pierre De Rop
Hello Paul, indeed, the DM4 code is very close to the old 3.2 API, and it would be unfortunate if breaking the API too much would make slower the adoption of the new version. I gave immense effort to bring to life the new thread model introduced by Marcel and Xander, and now we also have a nice ac