[CONTROLLER-1646] Milestone: Eliminate sal-schema-service Created: 27/Apr/17 Updated: 25/Jul/23 Resolved: 14/Nov/18 |
|
| Status: | Resolved |
| Project: | controller |
| Component/s: | mdsal |
| Affects Version/s: | None |
| Fix Version/s: | Fluorine |
| Type: | Bug | ||
| Reporter: | Robert Varga | Assignee: | Robert Varga |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 8327 |
| Description |
|
sal-schema-service is one of the remnants of our controller->mdsal split, leaving us with two services providing the same interface. Once BUG-8326 is done, we need to make this service a proxy to DOMSchemaService provided by the MD-SAL project. Then we need to deprecate the old SchemaService API, migrate all users and finally remove the proxy. |
| Comments |
| Comment by Robert Varga [ 28/Apr/17 ] |
|
This has interesting impact on startup, as we are assembling the same schemacontext twice. We also can wire up the proxy as is, without splitting it up. |
| Comment by Robert Varga [ 28/Apr/17 ] |
|
mdsal: controller: We should backport this as far as Boron. |
| Comment by Robert Varga [ 01/May/17 ] |
|
The proxy and deprecation patches are in, moving this issue back to confirmed, so it can act as a tracker for final removal. |
| Comment by Robert Varga [ 14/Nov/18 ] |