Re: atomic access to config values

Le 4 avr. 2018 19:37, "Mark Struberg" a écrit : But that's still problematic. you have request1 ongoing and call in the following order: ftpConfig.host();ftpConfig.port();// <- and here some config update happens ftpConfig.username(); So even if we update the whole

Re: atomic access to config values

But that's still problematic. you have request1 ongoing and call in the following order: ftpConfig.host();ftpConfig.port();// <- and here some config update happens ftpConfig.username(); So even if we update the whole ftpConfig 'at once' you will end up with mixed up information in this

Re: atomic access to config values

Since the cache is per instance we should just clear it on eviction at once IMHO the issue is: do you want to populate it at once too? tempted to say yes this means it can always be active but requires to be able to copy the current config state or prevent *any* update while populating such

Re: atomic access to config values

We should also enhance the support to include @Configuration. e.g. if you have some class like @Configuration(cacheFor=60, cacheUnit=TimeUnit.MINUTES) public class FtpConfigation {  String host();  Integer port();  String username();  String encryptedPwd();} Then you will likely resolve all

atomic access to config values

hi folks! please review the proposed solution for DELTASPIKE-1335 https://issues.apache.org/jira/browse/DELTASPIKE-1335 Not quite sure about startTransaction and ConfigTransation are the right terms. Happy to get feedback! txs and LieGrue,strub

[jira] [Commented] (DELTASPIKE-1335) allow atomic access to n different TypedResolver values

[ https://issues.apache.org/jira/browse/DELTASPIKE-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425772#comment-16425772 ] Mark Struberg commented on DELTASPIKE-1335: --- pushed a proposed new API for solving this

[jira] [Updated] (DELTASPIKE-1335) allow atomic access to n different TypedResolver values

[ https://issues.apache.org/jira/browse/DELTASPIKE-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg updated DELTASPIKE-1335: -- Summary: allow atomic access to n different TypedResolver values (was: allow

[jira] [Created] (DELTASPIKE-1335) allow atomic acces too n different TypedResolver values

Mark Struberg created DELTASPIKE-1335: - Summary: allow atomic acces too n different TypedResolver values Key: DELTASPIKE-1335 URL: https://issues.apache.org/jira/browse/DELTASPIKE-1335 Project:

[jira] [Commented] (DELTASPIKE-1277) Force refresh of cached config values

[ https://issues.apache.org/jira/browse/DELTASPIKE-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425333#comment-16425333 ] Mark Struberg commented on DELTASPIKE-1277: --- Implemented together with [~elexx] and

[jira] [Commented] (DELTASPIKE-1295) Make @ConfigProperty.converter optional when there is only one possible converter for the considered injected type

[ https://issues.apache.org/jira/browse/DELTASPIKE-1295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425328#comment-16425328 ] Mark Struberg commented on DELTASPIKE-1295: --- We should probably implement the same logic I

[jira] [Resolved] (DELTASPIKE-1325) actively release ConfigSources and ConfigFilters if they implement Autocloseable

[ https://issues.apache.org/jira/browse/DELTASPIKE-1325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved DELTASPIKE-1325. --- Resolution: Fixed > actively release ConfigSources and ConfigFilters if they

[jira] [Commented] (DELTASPIKE-1325) actively release ConfigSources and ConfigFilters if they implement Autocloseable

[ https://issues.apache.org/jira/browse/DELTASPIKE-1325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425305#comment-16425305 ] ASF subversion and git services commented on DELTASPIKE-1325: - Commit

[jira] [Resolved] (DELTASPIKE-1327) EnvironmentPropertyConfigSource is not scannable?

[ https://issues.apache.org/jira/browse/DELTASPIKE-1327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved DELTASPIKE-1327. --- Resolution: Fixed Assignee: Mark Struberg Fix Version/s: 1.9.0

[jira] [Commented] (DELTASPIKE-1327) EnvironmentPropertyConfigSource is not scannable?

[ https://issues.apache.org/jira/browse/DELTASPIKE-1327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425272#comment-16425272 ] ASF subversion and git services commented on DELTASPIKE-1327: - Commit

[jira] [Resolved] (DELTASPIKE-1322) clean up ConfigResolver

[ https://issues.apache.org/jira/browse/DELTASPIKE-1322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved DELTASPIKE-1322. --- Resolution: Fixed implementation details now got moved from API to impl > clean

Re: [DISCUSS] ds for cdi 1.2+ only

I'd go for: * 1.8.x: java7 + EE6This one is needed for older business applications. Yes, there are still servers running on Java7. 1.9.x: java8 + EE6There are also still a lot of WebSphere-8.5.x and JBoss EAP-6 servers in production. Those got updates to Java8 but are still EE6! This is