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

Align with proposed standards for MP Config property names defined by MicroProfile specs #162

Closed
njr-11 opened this issue Jun 6, 2019 · 0 comments · Fixed by #163
Closed
Assignees

Comments

@njr-11
Copy link
Contributor

njr-11 commented Jun 6, 2019

Under eclipse/microprofile#100, new requirements/guidance is provided on how MicroProfile specs should name MP Config properties that they define. These properties must start with mp.[spec-name].

Under eclipse/microprofile-config#420, there is a request to ban the / character in property names.

This issue is opened for MicroProfile Context Propagation to pre-emptively align our spec-defined MP Config property names with both of these such that they will remain valid regardless of whether both/just one/neither of these proposals are adopted.

Property names will be:
mp.context.ManagedExecutor.cleared
mp.context.ManagedExecutor.maxAsync
mp.context.ManagedExecutor.maxQueued
mp.context.ManagedExecutor.propagated
mp.context.ThreadContext.cleared
mp.context.ThreadContext.propagated
mp.context.ThreadContext.unchanged

@njr-11 njr-11 self-assigned this Jun 6, 2019
njr-11 added a commit to njr-11/microprofile-context-propagation that referenced this issue Jun 6, 2019
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

Successfully merging a pull request may close this issue.

1 participant