[
https://issues.apache.org/jira/browse/DELTASPIKE-1296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16266801#comment-16266801
]
Romain Manni-Bucau commented on DELTASPIKE-1296:
------------------------------------------------
If we register them at AfterBeanDiscovery phase we would be deterministic and
solve the inter extension issue.
Strictly speaking having a single AfterDeploymentValidation deltaspike
extension and sorting ourself all the extensions using this hook would make it
deterministic too and solve the original issue.
In any case current implementation is not usable since it leads to a
misbehavior in most cases cause using the SPI file for a PropertyFileConfig is
all but recommanded in all our doc and would lead to a simple ConfigSource so
is not justified.
> PropertyFileConfig doesn't work with internal extensions
> --------------------------------------------------------
>
> Key: DELTASPIKE-1296
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1296
> Project: DeltaSpike
> Issue Type: Bug
> Affects Versions: 1.8.0
> Reporter: Romain Manni-Bucau
> Assignee: Mark Struberg
>
> We register PropertyFileConfig in AfterDeploymentValidation hook but
> extensions potentially already read the config entries. Technically there is
> probably no blocker to do it earlier and we should probably ensure all our
> extensions read keys in AfterDeploymentValidation.
> My use case was a configured cron expression in the scheduler usage.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
