|
||||||||||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. 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
1) The autoconf resource processor should not wire to ConfigurationAdmin (or Metatype) of the management agent, as that one is private for the management agent. Instead, it should try to find one outside of this special space. It should still wire to the DeploymentAdmin and EventAdmin of the management agent though. Therefore I propose a slightly modified set of import statements that make this explicit.
Note that the ConfigurationAdmin of the management agent != Configuration Admin of the platform scope, and I think that's fine. If we decide that the platform scope should be able to configure specific aspects of the ACE MA, we should bridge those worlds instead of directly linking them.
2) I agree with your suggestion, fileinstall.autoconf should wire to the DeploymentAdmin of the management agent.