[MGNLOBS-12] Multiple node types event listener. Created: 05/Oct/11 Updated: 04/Nov/15 Resolved: 04/Nov/15 |
|
| Status: | Closed |
| Project: | Observation |
| Component/s: | None |
| Affects Version/s: | 1.2 |
| Fix Version/s: | backlog |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Danilo Ghirardelli | Assignee: | Teresa Miyar |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Template: |
|
| Patch included: |
Yes
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Date of First Response: |
| Description |
|
At the moment there is the possibility to set a single node type in a CommandEventListener, but in some cases this may not be enough. On the other side, without this class, you can set a restriction on node type on the "parent" listener configuration (the config node that is a parent of the node in which you define the listener class), and copy that entire configuration for each node type or subtype you need. |
| Comments |
| Comment by Michael Mühlebach [ 04/Nov/15 ] |
|
Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes. |