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.

Sign up for GitHub

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

Jump to bottom

SPI loading doesn't allow controlled overriding of instances to be used #9

Open
atsticks opened this issue Apr 1, 2017 · 0 comments
Open

SPI loading doesn't allow controlled overriding of instances to be used #9

atsticks opened this issue Apr 1, 2017 · 0 comments
Labels
enhancement

Comments

@atsticks
Copy link

atsticks commented Apr 1, 2017

Source: ServiceUtil.java:
The loader relies only on default ServiceLoader functionality. Depending on the classloading in place (which must not behave similar on each VM run), other instances of SPI may be returned. Furthermore there is no defined mechanism how one could override an SPI explicitly, if multiple implementation are registered.
A resolution how this can be solved can be found here:
ServiceContextManager.java,
ServiceContext.java
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@atsticks @amoAHCP