[
https://issues.apache.org/jira/browse/FELIX-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15875139#comment-15875139
]
David Jencks commented on FELIX-5549:
-------------------------------------
I have very little confidence that our words are communicating much. I don't
see any evidence of anything unusual from any of the output you have quoted,
but you seem to be saying there is behavior that isn't shown in the quoted
output but ought to be logged, judging by your code. I tries building your
project and got
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.3:compile (default-compile) on
project blueprint-ds-config-reload: Fatal error compiling: invalid target
release: 1.8 -> [Help 1]
I've looked at the existing integration tests and think that the situation you
have set up is the same as that tested in
org.apache.felix.scr.integration.ComponentFactoryTest
test_component_factory_optional_configuration_nomodify, which appears to
validate that the behavior is as I described. Could you take a look at this
test and see if it replicates what you are trying to show?
To reiterate, configuration activity should not affect the registered
ComponentFactory service in any externally visible way, but with no modify
method all the component instances created by calling newInstance will be
destroyed. If you are seeing the ComponentFactory service affected please show
this unequivocally in some logs. If you can record ds debug logging that
should show in detail what is going on.
> Factory component fails to reactivate after config changes
> ----------------------------------------------------------
>
> Key: FELIX-5549
> URL: https://issues.apache.org/jira/browse/FELIX-5549
> Project: Felix
> Issue Type: Bug
> Components: Declarative Services (SCR)
> Environment: Karaf 4.0.8
> Reporter: Alex Soto
>
> A factory component fails to reactive after the configuration changes.
> Initially, the component initializes normally. After it is in Active state,
> the configuration referenced by the component _configurationPid_ changes,
> which causes the component to not activate again.
> A minimal application demonstrating this behavior is available here:
> https://github.com/lexsoto/blueprint-ds-config-reload
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
