[
http://jira.amdatu.org/jira/browse/AMDATU-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bram de Kruijff resolved AMDATU-401.
------------------------------------
Assignee: Marcel Offermans (was: Bram de Kruijff)
Resolution: Fixed
Analysis:
1) FSUserAdminStorageConfigImpl itself implements ManagedService
-> OK, although not strictly necessary when using a DM ConfigurationDependecy
2) FSUserAdminStorageProviderActivator registers FSUserAdminStorageConfigImpl
under both FSUserAdminStorageConfig and ManagedService, without service.pid but
with a ConfigurationDependecy
-> Awkward, either use ConfigurationDependecy or DIY but then use a service.pid.
3) Due to my latest change, setting propagate to true, the service.pid is
propagated to the FSUserAdminStorageConfig service.
-> Error, now there are two ManagedService registration with same service.pid
Resolution:
Not sure if the propagate is really a good idea at all. It also feels a little
awkward that a non ManagedService registration recieves a service.pid(?).
Should DM maybe not propate service.*? Still reverting this still leaves a
ManagedService without service.pid which feels more awkward. Removing the
ManagedService registration deals with this awkwardness and resolves the issue
as well. Therefore choosing the latter solution.
> Tenant and Useradmin fs storage configuration fails in deployment
> -----------------------------------------------------------------
>
> Key: AMDATU-401
> URL: http://jira.amdatu.org/jira/browse/AMDATU-401
> Project: Amdatu
> Issue Type: Bug
> Components: Amdatu Core
> Affects Versions: 0.3.0-M0
> Reporter: Bram de Kruijff
> Assignee: Marcel Offermans
> Priority: Critical
> Fix For: 0.3.0-M0
>
>
> It appears that both Tenant and Useradmin fs storage configuration fail in
> deployment. This is caused by the fact that these services both use a PID in
> the form containing a '-'. The Felix File install interprets config files
> with a '-' as configurations for a Managed Service Factory rather then a
> Managed Service. See
> http://felix.apache.org/site/apache-felix-file-install.html for details on
> file install.
> Not sure this is a regression or if it actually never worked. As the
> integration test call configadmin directly they do not detect the problem and
> previous releases use the cassandra backstore by default which could also
> explain that none detected the issue.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Amdatu-developers mailing list
[email protected]
http://lists.amdatu.org/mailman/listinfo/amdatu-developers
