Remove CSS modules The CSS features are still installed until we can work out the ModuleInfoBackedContext/ClassLoaderStrategy situation that is currently provided by the ConfigManagerActivator. Change-Id: Id3b2cc287d17532482a2dd893c41e2dcd8d29ff0 Signed-off-by: Tom Pantelis <tompantelis@gmail.com> Signed-off-by: Robert Varga <robert.varga@pantheon.tech>
Fix checkstyle violations in sal-dom-broker-config and sal-binding-config Change-Id: I5cbd04bfb598481fc6b107f426cf01819ab8d4b2 Signed-off-by: Tom Pantelis <tompantelis@gmail.com>
sal-dom-broker-config: use lambdas This series of patches uses lambdas instead of anonymous classes for functional interfaces when possible. Lambdas are replaced with method references when appropriate. Change-Id: Iaf552c1e280034f8a465b46b9092a7df0cec5409 Signed-off-by: Stephen Kitt <skitt@redhat.com>
Move GlobalBundleScanningSchemaServiceImpl to its own bundle Moved the GlobalBundleScanningSchemaServiceImpl and the associated BundleActivator, SchemaServiceActivator, from sal-dom-broker to a new bundle sal-schema-service. A couple reasons for this. One is to break the circular service imports between sal-dom-broker and sal-distributed-datastore, where sal-distributed-datastore imports the SchemaService from sal-dom-broker and sal-dom-broker imports the DOMDataBroker from sal-distributed-datastore. The result of this was that if the sal-dom-broker blueprint container was restarted, it would also cause the sal-distributed-datastore container to restart, which isn't necessary/desirable. The other reason is that apps can register a SchemaContextListener as an OSGi service which is picked up by the GlobalBundleScanningSchemaServiceImpl. In terms of service usage this makes sal-dom-broker a dependency of the app bundle so if the app container restarts, it also restarts sal-dom-broker, sal-distributed-datastore etc which isn't desirable. So moving the GlobalBundleScanningSchemaServiceImpl to its own bundle alleviates both issues. Change-Id: I75d1009f6bfc1d80a19a61050703a1ca7e049575 Signed-off-by: Tom Pantelis <tpanteli@brocade.com>
Deprecate md-sal config modules Marked the md-sal dom/binding config yang modules, 01-md-sal.xml and associated Module classes as deprecated. Change-Id: Icbc24a0622f8b83173f656f9fa11003f270eaef3 Signed-off-by: Tom Pantelis <tpanteli@brocade.com>
Modify config Module impls to co-exist with blueprint Modified various config system Module implementation classes which have corresponding instances created and advertised via blueprint to obtain the instance in createInstance from the OSGi registry. The instance may not be available yet so it will wait. I added a WaitingServiceTracker class to encapsulate this logic using a ServiceTracker. For those modules that don't advertise services, createInstance simply returns a noop AutoCloseable since the components are created via blueprint. I also added the new disable-osgi-service-registration flag to the corresponding service yang identities to prevent the CSS from duplicating the service registrations. This patch also adds the blueprint bundle to the mdsal features and "turns on" blueprint. Change-Id: I60099c82a2a248fc233ad930c4808d6ab19ea881 Signed-off-by: Tom Pantelis <tpanteli@brocade.com>
Add blueprint wiring to sal-dom-broker Change-Id: I48959c4ebf02881dfb29d051b35c45de3effc650 Signed-off-by: Tom Pantelis <tpanteli@brocade.com>
Bug 4035: Extract dom-config from core-api and broker-impl This patch introduces two new artefacts sal-dom-config and sal-dom-broker-config which hosts all config subsystem related MD-SAL DOM Broker implementation. This patch is required for MD-SAL split in order to not have cyclic dependency between controller and md-sal project. Change-Id: Ic93c583c07ae3e088dcf0e74cbdaaf627a8e79f6 Signed-off-by: Tony Tkacik <ttkacik@cisco.com>