Age | Commit message (Collapse) | Author | Files | Lines |
|
Changes made:
* Created generalized version of core/utils/dblib as core/utils/common
* Deprecated core/utils/dblib package
Change-Id: I0992c43910278fbe254674d1e39d7e4fcad0a592
Issue-ID: CCSDK-168
Signed-off-by: Rich Tabedzki <richard.tabedzki@att.com>
|
|
Related to exception handling.
@Override method
Redundant code and resulable parameters
Issue-Id:CCSDK-87
Change-Id: I82e2aad453edf5cd647c87322fc75b2a56c37566
Signed-off-by: Bharat saraswal <bharat.saraswal@huawei.com>
|
|
When looking at the existing uses of BundleActivator(s), it became
immediately clear that other parts of the code have a strategy based
properties file resolution very similar to those abstracted by dblib.
This change aggregates a separate utils bundle for this functionality,
which is further abstracted for potential reuse with other use cases.
The next use case is in the sli bundle, which will be handled in
a follow-up patch.
Issue-Id: SDNC-54
Change-Id: Ie4d4bb679617474b1983e6044c08cca1742b9893
Signed-off-by: Ryan Goulding <ryandgoulding@gmail.com>
|
|
Code sanitation-- remove unused imports.
Issue-Id: SDNC-79
Change-Id: I5306a9b90f302086459fcac98d04f541ba7c79a4
Signed-off-by: Ryan Goulding <ryandgoulding@gmail.com>
|
|
Addresses the inherit race conditions associated with the
BundleActivator abstraction. From lessons learned in OpenDaylight
project, dependency injection and service injection via Aries Blueprint
is faster, more deterministic, and has better error messaging than
using BundleActivator(s).
This change addresses several aspects:
1) DBLIBResourceActivator is changed to DBLIBResourceProvider.
This was done in order to imply that this is no longer an
Activator or subclass of an Activator. The class is a POJO.
2) DBLIBResourceProvider is split from a single monolithic method
into several more manageable and better documented methods.
3) Documentation surrounding the resolution of the DB properties
is added so that a developer can more easily identify the
strategy (priority) used for resolving properties.
4) dblib-blueprint.xml is added. This is used to register the
configuration bean (DBLIBResourceProvider), and pass it as
an argument to the actual Service (DBLIBResourceManager).
5) Tests are added to test the functionality and resolution of
the properties file loading.
Issue-Id: SDNC-54
Change-Id: Ie9d5fb423ae7a67e9aec026c78321537399cc308
Signed-off-by: Ryan Goulding <ryandgoulding@gmail.com>
|