[
https://issues.apache.org/jira/browse/FELIX-5817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raymond Augé updated FELIX-5817:
--------------------------------
Description:
Over and over again developers ask me if it's possible to persistently disable
components. We all know the answer, but I know for a fact that more than one
company has written a little tool which provides this feature to their own
developers via some form of configuration.
I'm hoping with this issue to open the discussion about making this a feature
of SCR itself so that we don't have to have external agent do it.
Use cases revolve mostly around customer maintenance scenarios:
# to deal with a bug temporarily while a fix is being developed (maybe over
the course of days or weeks)
# to deal with a customization where the component behavior needs to be
changed but the original component should not be relegated to the background..
it should be taken completely out of operation (but not the whole bundle)
# etc.
was:
Over and over again developers ask me if it's possible to persistently disable
components. We all know the answer, but I know for a fact that more than one
company has written a little tool which provides this feature to their own
developers via some form of configuration.
I'm hoping with this issue to open the discussion about making this a feature
of SCR itself so that we don't have to have external agent do it.
> mechanism to persist component disable
> --------------------------------------
>
> Key: FELIX-5817
> URL: https://issues.apache.org/jira/browse/FELIX-5817
> Project: Felix
> Issue Type: Improvement
> Components: Declarative Services (SCR)
> Reporter: Raymond Augé
> Priority: Major
>
> Over and over again developers ask me if it's possible to persistently
> disable components. We all know the answer, but I know for a fact that more
> than one company has written a little tool which provides this feature to
> their own developers via some form of configuration.
> I'm hoping with this issue to open the discussion about making this a feature
> of SCR itself so that we don't have to have external agent do it.
> Use cases revolve mostly around customer maintenance scenarios:
> # to deal with a bug temporarily while a fix is being developed (maybe over
> the course of days or weeks)
> # to deal with a customization where the component behavior needs to be
> changed but the original component should not be relegated to the
> background.. it should be taken completely out of operation (but not the
> whole bundle)
> # etc.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
