[CAMEL-4358] Refactoring of management code to remove cycles and clearly separate between API and impl

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.8.0
• Fix Version/s: 2.9.0
• Component/s: camel-core
• Patch Info: Patch Available
• Estimated Complexity: Unknown
• Assignee: Christian Schneider
• Reporter: Christian Schneider
• Created: 19/Aug/11 15:58
• Updated: 14/Sep/11 12:10
• Resolved: 14/Sep/11 12:10

Description

Currently the management code (org.apache.camel.management.*) contains a mix of implementation code and APIs. This leads to cycle in the management code as well as to bigger cycles involving all of camel-core.

So I propose to do several changes:

• move interfaces and annotations that form the API to camel.spi.management. As these are probably not used by external components or user code no compatibility classes are created
• create new package camel.suppport for classes that implement API or SPI classes and are expected to be extended by many impl classes. classes in support may only access the camel API and SPI
• Move EventNotifierSupport and ServiceSupport to this package. Create deprecate dummys in the old locations to avoid breaking older code
• Move DefaultEventFactory from management to management.event

I will post a patch shortly for review