You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MicroProfile Concurrency very nearly introduced a slightly different way of doing the same thing for override of its own config annotations, but having discovered the FaultTolerance approach, is now switching to align with the FaultTolerance approach so that MicroProfile specs can be consistent.
It would be helpful if MicroProfile Config spec itself defined the convention, because that is where new specifications will look before coming up with their own approaches.
The text was updated successfully, but these errors were encountered:
Closing because this issue has been taken up by MicroProfile in general, and is being tracked under the following issue instead under the general MicroProfile repository: eclipse/microprofile#98
MicroProfile Fault Tolerance already defines a way to use MicroProfile Config to override annotation values,
https://download.eclipse.org/microprofile/microprofile-fault-tolerance-2.0/microprofile-fault-tolerance-spec.html#configuration
MicroProfile Concurrency very nearly introduced a slightly different way of doing the same thing for override of its own config annotations, but having discovered the FaultTolerance approach, is now switching to align with the FaultTolerance approach so that MicroProfile specs can be consistent.
It would be helpful if MicroProfile Config spec itself defined the convention, because that is where new specifications will look before coming up with their own approaches.
The text was updated successfully, but these errors were encountered: