| // |
| // Licensed under the Apache License, Version 2.0 (the "License"); |
| // you may not use this file except in compliance with the License. |
| // You may obtain a copy of the License at |
| // |
| // http://www.apache.org/licenses/LICENSE-2.0 |
| // |
| // Unless required by applicable law or agreed to in writing, software |
| // distributed under the License is distributed on an "AS IS" BASIS, |
| // WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. |
| // See the License for the specific language governing permissions and |
| // limitations under the License. |
| // |
| |
| === Supported Events |
| |
| There are 3 types of events: |
| |
| * Configuration change event. |
| * Features repository added/removed event. |
| * Features installed/uninstalled event. |
| |
| Optionally (by installing the corresponding features), Cellar supports the following additional events: |
| |
| * EventAdmin |
| * OBR |
| |
| For each of the event types above a group may be configured to enabled synchronization, and to provide |
| a whitelist/blacklist of specific event IDs. |
| |
| For instance, the default group is configured to allow synchronization of configuration. This means that |
| whenever a change occurs via the config admin to a specific PID, the change will pass to the distributed |
| memory of the default group and will also be broadcasted to all other default group nodes using the topic. |
| |
| This happens for all PIDs but not for org.apache.karaf.cellar.node which is marked as blacklisted |
| and will never be written or read from the distributed memory, nor will be broadcasted via the topic. |
| |
| The user can add/remove any PID they wish to the whitelist/blacklist. |
