[
https://issues.apache.org/jira/browse/ACE-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Offermans resolved ACE-53.
---------------------------------
Resolution: Fixed
Assignee: Toni Menzel
Checked to validate that this actually works:
1) Add the AutoConfig resource processor as an artifact to the repository. You
can get a snapshot copy of that by building the Apache Felix DeploymentAdmin
project, which contains an implementation of this. The OSGi specification
explains the exact file format being used.
2) Add a resource in the metatype xml format as an artifact to the repository
and link it to a target (via feature and distribution).
The fact that you've now added a resource that is recognized as an AutoConfig
artifact is enough for ACE to automatically deploy the appropriate resource
processor to that target as well. We probably need to document this process in
more detail on the site, but these are the basic steps.
> Ability to send configuration data to gateways
> ----------------------------------------------
>
> Key: ACE-53
> URL: https://issues.apache.org/jira/browse/ACE-53
> Project: Ace
> Issue Type: New Feature
> Reporter: Toni Menzel
> Assignee: Toni Menzel
>
> In terms of the "passive gateway" scenario, it would be good if the server
> could serve configuration data (in standard format at best, ConfigAdmin Spec)
> to their management agents.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
