[TRNSPRTPCE-391] Reorganise dependency injection in Service Handler Created: 22/Jan/21 Updated: 03/Sep/21 Resolved: 05/Feb/21 |
|
| Status: | Verified |
| Project: | transportpce |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Medium |
| Reporter: | Gilles Thouenon | Assignee: | Gilles Thouenon |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 0 minutes | ||
| Time Spent: | 2 days | ||
| Original Estimate: | Not Specified | ||
| Description |
|
When we install the T-API feature, instead of using the existing ServiceHandler instance that allows access to existing services in the ServiceDatastore, a new service handler instance is created through the ServiceHandlerOperation interface. Services created on the first service handler instance are not visible through the T-API instance. Review all dependency injection in Service Handler to avoid any manual instance creation by taking advantage of blueprint dependency injection (as singleton) |