[jira] [Resolved] (FELIX-3971) [DS] SingleDynamicCustomizer doesn't respond correctly to configuration update events.

[ https://issues.apache.org/jira/browse/FELIX-3971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks resolved FELIX-3971. - Resolution: Fixed I'm going to close this issue and consider further discussions about factory c

[jira] [Closed] (FELIX-3971) [DS] SingleDynamicCustomizer doesn't respond correctly to configuration update events.

[ https://issues.apache.org/jira/browse/FELIX-3971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed FELIX-3971. --- > [DS] SingleDynamicCustomizer doesn't respond correctly to configuration > update events. > ---

[jira] [Closed] (FELIX-4224) [DS] Dependency manager can be active but not have m_bindMethods set

[ https://issues.apache.org/jira/browse/FELIX-4224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed FELIX-4224. --- > [DS] Dependency manager can be active but not have m_bindMethods set >

[jira] [Resolved] (FELIX-4224) [DS] Dependency manager can be active but not have m_bindMethods set

[ https://issues.apache.org/jira/browse/FELIX-4224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks resolved FELIX-4224. - Resolution: Fixed m_bindMethods was made volatile in a commit for FELIX-4223 > [DS] Dependency m

[jira] [Resolved] (FELIX-4022) [DS] Deleting a configuration is supposed to deactivate the component unconditionally

[ https://issues.apache.org/jira/browse/FELIX-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks resolved FELIX-4022. - Resolution: Won't Fix Our behavior is correct, the spec needs to be clarified. > [DS] Deleting a

[jira] [Updated] (FELIX-3651) [DS] Properly support configuration location binding and targeted pids

[ https://issues.apache.org/jira/browse/FELIX-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks updated FELIX-3651: Summary: [DS] Properly support configuration location binding and targeted pids (was: Properly sup

[jira] [Resolved] (FELIX-3651) [DS] Properly support configuration location binding and targeted pids

[ https://issues.apache.org/jira/browse/FELIX-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks resolved FELIX-3651. - Resolution: Fixed > [DS] Properly support configuration location binding and targeted pids >

[jira] [Closed] (FELIX-3651) [DS] Properly support configuration location binding and targeted pids

[ https://issues.apache.org/jira/browse/FELIX-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed FELIX-3651. --- > [DS] Properly support configuration location binding and targeted pids > --

[jira] [Updated] (FELIX-3584) [DS] Handle new LOCATION_CHANGED event

[ https://issues.apache.org/jira/browse/FELIX-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks updated FELIX-3584: Summary: [DS] Handle new LOCATION_CHANGED event (was: Handle new LOCATION_CHANGED event) > [DS] H

[jira] [Closed] (FELIX-4223) [DS] DependencyManager filter should be set up in enable, not activate, to avoid race conditions

[ https://issues.apache.org/jira/browse/FELIX-4223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed FELIX-4223. --- > [DS] DependencyManager filter should be set up in enable, not activate, to > avoid race conditions > -

[jira] [Closed] (FELIX-3584) [DS] Handle new LOCATION_CHANGED event

[ https://issues.apache.org/jira/browse/FELIX-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed FELIX-3584. --- > [DS] Handle new LOCATION_CHANGED event > -- > > Key

[jira] [Resolved] (FELIX-3584) [DS] Handle new LOCATION_CHANGED event

[ https://issues.apache.org/jira/browse/FELIX-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks resolved FELIX-3584. - Resolution: Fixed > [DS] Handle new LOCATION_CHANGED event >

[jira] [Closed] (FELIX-4189) [DS] DS should not hold any lock while calling bundleContext#getService

[ https://issues.apache.org/jira/browse/FELIX-4189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed FELIX-4189. --- > [DS] DS should not hold any lock while calling bundleContext#getService > -

[jira] [Updated] (FELIX-4188) [DS] If a bundle is stopped while the SCR extender is being stopped, the callback for the STOPPING event returns before full deactivation

[ https://issues.apache.org/jira/browse/FELIX-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks updated FELIX-4188: Summary: [DS] If a bundle is stopped while the SCR extender is being stopped, the callback for the

[jira] [Closed] (FELIX-4188) [DS] If a bundle is stopped while the SCR extender is being stopped, the callback for the STOPPING event returns before full deactivation

[ https://issues.apache.org/jira/browse/FELIX-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed FELIX-4188. --- > [DS] If a bundle is stopped while the SCR extender is being stopped, the > callback for the STOPPING e

[jira] [Resolved] (FELIX-4223) [DS] DependencyManager filter should be set up in enable, not activate, to avoid race conditions

[ https://issues.apache.org/jira/browse/FELIX-4223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks resolved FELIX-4223. - Resolution: Fixed > [DS] DependencyManager filter should be set up in enable, not activate, to >

[jira] [Closed] (FELIX-4166) [DS] Removing required dependency before component is created leaves service registered

[ https://issues.apache.org/jira/browse/FELIX-4166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed FELIX-4166. --- > [DS] Removing required dependency before component is created leaves service > registered > --

[jira] [Closed] (FELIX-4090) [DS] ActivateMethod.ACTIVATE_TYPES_DS11 and ACTIVATE_TYPES_DS10 should be static final

[ https://issues.apache.org/jira/browse/FELIX-4090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed FELIX-4090. --- > [DS] ActivateMethod.ACTIVATE_TYPES_DS11 and ACTIVATE_TYPES_DS10 should be > static final > ---

[jira] [Closed] (FELIX-4171) [DS] possible DependencyManager NPE during cleanup after failure to activate a component

[ https://issues.apache.org/jira/browse/FELIX-4171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed FELIX-4171. --- > [DS] possible DependencyManager NPE during cleanup after failure to activate > a component > -

[jira] [Updated] (FELIX-4090) [DS] ActivateMethod.ACTIVATE_TYPES_DS11 and ACTIVATE_TYPES_DS10 should be static final

[ https://issues.apache.org/jira/browse/FELIX-4090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks updated FELIX-4090: Summary: [DS] ActivateMethod.ACTIVATE_TYPES_DS11 and ACTIVATE_TYPES_DS10 should be static final (w

[jira] [Resolved] (FELIX-4171) [DS] possible DependencyManager NPE during cleanup after failure to activate a component

[ https://issues.apache.org/jira/browse/FELIX-4171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks resolved FELIX-4171. - Resolution: Fixed > [DS] possible DependencyManager NPE during cleanup after failure to activate

[jira] [Resolved] (FELIX-4166) [DS] Removing required dependency before component is created leaves service registered

[ https://issues.apache.org/jira/browse/FELIX-4166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks resolved FELIX-4166. - Resolution: Fixed > [DS] Removing required dependency before component is created leaves service

[jira] [Closed] (FELIX-4070) [DS] Reduce or eliminate use of States in command pattern

[ https://issues.apache.org/jira/browse/FELIX-4070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed FELIX-4070. --- > [DS] Reduce or eliminate use of States in command pattern > ---

[jira] [Closed] (FELIX-4088) [DS] NPE from SCR service unregistration

[ https://issues.apache.org/jira/browse/FELIX-4088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed FELIX-4088. --- > [DS] NPE from SCR service unregistration > > >

[jira] [Resolved] (FELIX-4070) [DS] Reduce or eliminate use of States in command pattern

[ https://issues.apache.org/jira/browse/FELIX-4070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks resolved FELIX-4070. - Resolution: Fixed > [DS] Reduce or eliminate use of States in command pattern > -

[jira] [Updated] (FELIX-4088) [DS] NPE from SCR service unregistration

[ https://issues.apache.org/jira/browse/FELIX-4088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks updated FELIX-4088: Summary: [DS] NPE from SCR service unregistration (was: NPE from SCR service unregistration) > [D

[jira] [Resolved] (FELIX-4088) [DS] NPE from SCR service unregistration

[ https://issues.apache.org/jira/browse/FELIX-4088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks resolved FELIX-4088. - Resolution: Fixed > [DS] NPE from SCR service unregistration > --

[jira] [Resolved] (FELIX-4088) [DS] NPE from SCR service unregistration

[ https://issues.apache.org/jira/browse/FELIX-4088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks resolved FELIX-4088. - Resolution: Fixed > [DS] NPE from SCR service unregistration > --

[jira] [Reopened] (FELIX-4088) [DS] NPE from SCR service unregistration

[ https://issues.apache.org/jira/browse/FELIX-4088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks reopened FELIX-4088: - Assignee: David Jencks > [DS] NPE from SCR service unregistration > ---

[jira] [Closed] (FELIX-4088) [DS] NPE from SCR service unregistration

[ https://issues.apache.org/jira/browse/FELIX-4088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed FELIX-4088. --- > [DS] NPE from SCR service unregistration > > >

[jira] [Resolved] (FELIX-4057) [DS] Use Findbugs, and fix located problems

[ https://issues.apache.org/jira/browse/FELIX-4057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks resolved FELIX-4057. - Resolution: Fixed > [DS] Use Findbugs, and fix located problems > ---

[jira] [Closed] (FELIX-4057) [DS] Use Findbugs, and fix located problems

[ https://issues.apache.org/jira/browse/FELIX-4057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed FELIX-4057. --- > [DS] Use Findbugs, and fix located problems > --- > >

[jira] [Closed] (FELIX-4069) [DS] ConcurrentModificationException in ServiceFactoryComponentManager

[ https://issues.apache.org/jira/browse/FELIX-4069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed FELIX-4069. --- > [DS] ConcurrentModificationException in ServiceFactoryComponentManager > --

[jira] [Updated] (FELIX-4069) [DS] ConcurrentModificationException in ServiceFactoryComponentManager

[ https://issues.apache.org/jira/browse/FELIX-4069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks updated FELIX-4069: Summary: [DS] ConcurrentModificationException in ServiceFactoryComponentManager (was: ConcurrentMo

[jira] [Closed] (FELIX-4055) [DS] Component instance unset but remains in Active state

[ https://issues.apache.org/jira/browse/FELIX-4055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed FELIX-4055. --- > [DS] Component instance unset but remains in Active state > ---

[jira] [Resolved] (FELIX-4055) [DS] Component instance unset but remains in Active state

[ https://issues.apache.org/jira/browse/FELIX-4055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks resolved FELIX-4055. - Resolution: Fixed > [DS] Component instance unset but remains in Active state > -

[jira] [Closed] (FELIX-4020) [DS] A reference being unregistered between checking for references available and actual binding may get bound anyway

[ https://issues.apache.org/jira/browse/FELIX-4020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed FELIX-4020. --- > [DS] A reference being unregistered between checking for references available > and actual binding may

[jira] [Closed] (FELIX-4031) [DS] Respond better to InterruptedException

[ https://issues.apache.org/jira/browse/FELIX-4031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed FELIX-4031. --- > [DS] Respond better to InterruptedException > --- > >

[jira] [Closed] (FELIX-3975) [DS] Give ParseException cause to move out of the stone age

[ https://issues.apache.org/jira/browse/FELIX-3975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed FELIX-3975. --- > [DS] Give ParseException cause to move out of the stone age > -

[jira] [Closed] (FELIX-4000) [DS] ConcurrentModificationException in AbstractComponentManager iterating through m_dependencyManagers

[ https://issues.apache.org/jira/browse/FELIX-4000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed FELIX-4000. --- > [DS] ConcurrentModificationException in AbstractComponentManager iterating > through m_dependencyManag

[jira] [Closed] (FELIX-3991) [DS] component deactivation may not complete properly with enough threads

[ https://issues.apache.org/jira/browse/FELIX-3991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed FELIX-3991. --- > [DS] component deactivation may not complete properly with enough threads > ---

[jira] [Closed] (FELIX-4004) [DS] ConcurrentModificationException in DependencyManager.open()

[ https://issues.apache.org/jira/browse/FELIX-4004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed FELIX-4004. --- > [DS] ConcurrentModificationException in DependencyManager.open() >

[jira] [Closed] (FELIX-4006) [DS] While disposing a component, it's possible to unbind a reference that wasn't bound.

[ https://issues.apache.org/jira/browse/FELIX-4006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed FELIX-4006. --- > [DS] While disposing a component, it's possible to unbind a reference that > wasn't bound. > -

[jira] [Closed] (FELIX-4011) [DS] code refactoring/simplification

[ https://issues.apache.org/jira/browse/FELIX-4011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed FELIX-4011. --- > [DS] code refactoring/simplification > > > Key: FE

[jira] [Closed] (FELIX-3952) [DS] service events can go missing resulting in hang

[ https://issues.apache.org/jira/browse/FELIX-3952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed FELIX-3952. --- > [DS] service events can go missing resulting in hang >

[jira] [Closed] (FELIX-3915) [DS] Timing hole between ComponentHolder initial config and registration

[ https://issues.apache.org/jira/browse/FELIX-3915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed FELIX-3915. --- > [DS] Timing hole between ComponentHolder initial config and registration >

[jira] [Closed] (FELIX-3967) [DS] NPE in DependencyManager$AbstractCustomizer.isSatisfied

[ https://issues.apache.org/jira/browse/FELIX-3967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed FELIX-3967. --- > [DS] NPE in DependencyManager$AbstractCustomizer.isSatisfied >

Re: Why DependencyManager rather than DS?

Hi Marcel, thanks for the explanations…. more quibbling inline :-) On Oct 15, 2013, at 1:33 PM, Marcel Offermans wrote: > Hello David, > > On Oct 15, 2013, at 19:51 PM, David Jencks wrote: > >> After seeing a lot of commit activity on DependencyManager I decided to try >> to understand what

[jira] [Commented] (FELIX-2923) Get a ServiceFactory.getService() resulted in a cycle message when registering a service inside a DS activation method

[ https://issues.apache.org/jira/browse/FELIX-2923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13795759#comment-13795759 ] David Jencks commented on FELIX-2923: - I'm not sure you can make this work with a sepa

Re: Why DependencyManager rather than DS?

Hello David, On Oct 15, 2013, at 19:51 PM, David Jencks wrote: > After seeing a lot of commit activity on DependencyManager I decided to try > to understand what it's for, and after looking at the documentation I'm still > not sure. It looks to me like the main feature is a fluent api that pr

Re: Why DependencyManager rather than DS?

On 10/15/13 13:51 , David Jencks wrote: After seeing a lot of commit activity on DependencyManager I decided to try to understand what it's for, and after looking at the documentation I'm still not sure. It looks to me like the main feature is a fluent api that provides something like DS, alt

[jira] [Commented] (FELIX-2923) Get a ServiceFactory.getService() resulted in a cycle message when registering a service inside a DS activation method

[ https://issues.apache.org/jira/browse/FELIX-2923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13795538#comment-13795538 ] David Humeniuk commented on FELIX-2923: --- I can try the latest snapshot at some point

Why DependencyManager rather than DS?

After seeing a lot of commit activity on DependencyManager I decided to try to understand what it's for, and after looking at the documentation I'm still not sure. It looks to me like the main feature is a fluent api that provides something like DS, although less declaratively, and then there a

[jira] [Updated] (FELIX-4285) Remove abstract modifier from DependencyActivatorBase.destroy()

[ https://issues.apache.org/jira/browse/FELIX-4285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] M. van Cuijk updated FELIX-4285: Attachment: FELIX-4285.patch > Remove abstract modifier from DependencyActivatorBase.destroy() > --

[jira] [Created] (FELIX-4285) Remove abstract modifier from DependencyActivatorBase.destroy()

M. van Cuijk created FELIX-4285: --- Summary: Remove abstract modifier from DependencyActivatorBase.destroy() Key: FELIX-4285 URL: https://issues.apache.org/jira/browse/FELIX-4285 Project: Felix