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
I believe shortly that a Jakarta Configuration will be a glue to configuration such as CDI does to communicate among specifications.
It is essential to have a unique configuration for the whole specification, to get reliability, and reusability, to reduce the number of bugs, and so on.
Looking at several platforms, we have several configurations that require more than properties, such as JPA connection, NoSQL client, JMS connection, etc.
It will be terrific if we have support for a more dynamic type such as a Map<String, String>.
It uses the prefix as an injection, and then it will put a key/pair dynamically. So, given this properties:
I believe shortly that a Jakarta Configuration will be a glue to configuration such as CDI does to communicate among specifications.
It is essential to have a unique configuration for the whole specification, to get reliability, and reusability, to reduce the number of bugs, and so on.
Looking at several platforms, we have several configurations that require more than properties, such as JPA connection, NoSQL client, JMS connection, etc.
It will be terrific if we have support for a more dynamic type such as a Map<String, String>.
It uses the prefix as an injection, and then it will put a key/pair dynamically. So, given this properties:
Using the injection:
It will provide the following keys:
The text was updated successfully, but these errors were encountered: