[
https://issues.apache.org/jira/browse/FELIX-895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680670#action_12680670
]
Filippo Diotalevi commented on FELIX-895:
-----------------------------------------
I'm experiencing the same bug. It's definitely a major bug, configurations are
not handled correctly inside FileInstall.
I'm working on a patch right now.
> File Install treats configuration files with identical subnames as the same
> configuration
> -----------------------------------------------------------------------------------------
>
> Key: FELIX-895
> URL: https://issues.apache.org/jira/browse/FELIX-895
> Project: Felix
> Issue Type: Bug
> Components: File Install
> Environment: NA
> Reporter: Paul Neyens
> Assignee: Peter Kriens
>
> Suppose you have two ManagedServiceFactory instances registered with pids
> 'com.acme.abc' and 'com.acme.xyz'
> To configure a default instance for each of the factories I created two .cfg
> files to be handled by File Install: com.acme.xyz-default.cfg and
> com.acme.abc-default.cfg
> What seems to happen is that File Install creates a first configuration
> (correctly) and then updates that configuration to the contents of the second
> configuration file. Apparently because the subname is the same. (filename ::=
> <pid> ( '-' <subname> )? '.cfg')
> Possible fix: File Install (class DirectoryWatcher) uses property
> _alias_factory_pid to identify and retrieve the configurations it manages.
> The value for this property is currently set to <subname>. A possible fix
> could be to use <pid>-<subname> (or even <filename>) as identification value.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.