Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FhirRegistry: dynamic resource CodeSystem,ValueSet loading #4223

Open
gdecagna opened this issue May 19, 2023 · 1 comment
Open

FhirRegistry: dynamic resource CodeSystem,ValueSet loading #4223

gdecagna opened this issue May 19, 2023 · 1 comment

Comments

@gdecagna
Copy link

Describe the bug
dynamic resource CodeSystem, ValueSet loading

Environment
5.1.1

To Reproduce
Steps to reproduce the behavior:

Expected behavior
dynamic reloading of resources

Additional context
FhirRegistry: I used the PackageRegistryResourceProvider procedure to register a set of CodeSystem and ValueSet resources.
This procedure, inserted in a jar located in the userLib, correctly loads the resources present in the .index.json file at start Up.
Is it possible to reload this procedure via URL command or other without restarting the server?
The goal is to edit the jar, copy it into the userLib and reload it without restarting the whole system.

@gdecagna gdecagna added the bug Something isn't working label May 19, 2023
@lmsurpre lmsurpre removed the bug Something isn't working label Jun 19, 2023
@lmsurpre
Copy link
Member

The RegistryResourceProviders are discovered during startup (using the java ServiceLoader pattern) and so registering new providers is not supported at runtime.

That said, it should be possible to implement a provider that can change what it provides dynamically. At one point, our ExtensionSearchParametersResourceProvider worked liked that (prior to https://github.com/LinuxForHealth/FHIR/pull/2942/files).

It might also be possible to invent a new way to register a new provider at runtime (e.g. via FHIRRegistry#addProvider()) but that is not exposed at the server level at this time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants