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

Applications are not 1:1 with class loaders #546

Open
2 of 4 tasks
dmlloyd opened this issue Mar 14, 2020 · 0 comments
Open
2 of 4 tasks

Applications are not 1:1 with class loaders #546

dmlloyd opened this issue Mar 14, 2020 · 0 comments
Labels
use case 💡 An issue which illustrates a desired use case for the specification

Comments

@dmlloyd
Copy link
Contributor

dmlloyd commented Mar 14, 2020

Description

As a:

  • Application user/user of the configuration itself
  • API user (application developer)
  • SPI user (container or runtime developer)
  • Specification implementer

...I need to be able to:

Break the 1:1 mapping between class loaders and configurations.

...which enables me to:

  • Have an application which spans multiple class loaders, yet shares one configuration.
  • Have a configuration which spans/is used by multiple applications.

Note that some containers rely on a 1:1 mapping; they should continue to be supported by any proposed solution.

Relates to #471, #472.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
use case 💡 An issue which illustrates a desired use case for the specification
Projects
None yet
Development

No branches or pull requests

1 participant