[MDSAL-290] DOMSchemaService has only OSGI-dependent implementation Created: 11/Aug/17  Updated: 09/Mar/18  Resolved: 15/Aug/17

Status: Resolved
Project: mdsal
Component/s: DOM runtime
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Martin Dindoffer Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

Issue Links:
Duplicate
duplicates MDSAL-248 Split out OsgiBundleScanningSchemaSer... Resolved
External issue ID: 8980

 Description   

OsgiBundleScanningSchemaService should be replaced by a platform-independent SchemaService.

 Comments   
Comment by Robert Varga [ 15/Aug/17 ]

What should the proposed implementation work like?

Comment by Juraj Veverka [ 15/Aug/17 ]

OsgiBundleScanningSchemaService will be renamed to ModelScanningSchemaService
It is necessary to create new interface org.opendaylight.mdsal.dom.broker.osgi.ServiceScanner which will have OSGi dependent implementation in ODL. ModelScanningSchemaService will use ServiceScanner implementation to interact with OSGi in karaf runtime. In Java SE runtime different implementation of ServiceScanner will be provided which will do noop or will have it's own registry of models.

Main point is that ModelScanningSchemaService has no compile dependency on org.osgi.*

Comment by Martin Dindoffer [ 15/Aug/17 ]

This is actually a duplicate of https://bugs.opendaylight.org/show_bug.cgi?id=8326

Generated at Wed Feb 07 20:09:24 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.