| commit | eb790498dacf46fc594b93bf62a6e17f686af62e | [log] [tgz] |
|---|---|---|
| author | Ryan Goulding <ryandgoulding@gmail.com> | Thu Sep 14 12:37:10 2017 -0400 |
| committer | Ryan Goulding <ryandgoulding@gmail.com> | Thu Sep 14 12:40:13 2017 -0400 |
| tree | 3acba84982203162bc41758391183ae12851b082 | |
| parent | bd920facad4f9ce5e8651acb6c477446106e892f [diff] |
Fix SDNC service registration Instead of registgering services via BundleActivator(s), use blueprint instead. This change deletes the RecordingActivator, as it was just used to kickstart the service registration using felix dm. The idea here is to instead use blueprint through recording-blueprint.xml. The decision was also made to register the Service(s) using the implementation class name instead of the interface class name for backwards compatibility reasons. In all reality, registering Service(s) under the implementation name is less future proof since clients are no longer able to easily swap in a separate implementation Service. In the future, we should consider finding usages of this Service and ensuring that they poll for the interface rather than the implementation. However, that is separate from this change and is considered future work. Issue-Id: SDNC-54 Change-Id: I757bb90f91d114668c153ec5debb5c65af44452a Signed-off-by: Ryan Goulding <ryandgoulding@gmail.com>
This source repository contains the code for the core SDN Controller components. To compile this code:
Make sure your local Maven settings file ($HOME/.m2/settings.xml) contains references to the ONAP repositories and OpenDaylight repositories.
To compile, run "mvn clean install".