[
https://issues.apache.org/jira/browse/DELTASPIKE-1468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17805344#comment-17805344
]
ASF subversion and git services commented on DELTASPIKE-1468:
-------------------------------------------------------------
Commit e7357d14309b30e019ee46e6a73d507d04138b1e in deltaspike's branch
refs/heads/master from Thomas Andraschko
[ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=e7357d143 ]
Merge pull request #138 from phillipross/topic/fix/DELTASPIKE-1468
add explicit dependent scope to PrincipalProvider and TimestampsProvider beans
> AuditProvider (PrincipalProvider/TimestampsProvider) not working
> ----------------------------------------------------------------
>
> Key: DELTASPIKE-1468
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1468
> Project: DeltaSpike
> Issue Type: New Feature
> Security Level: public(Regular issues)
> Components: JPA-Module
> Affects Versions: 2.0
> Environment: symptom exhibited on Payara6 WELD
> Reporter: Phillip Ross
> Priority: Blocker
>
> PrincipalProvider and TimestampsProvider stop working in v2.0 (probably since
> DELTASPIKE-1466) as they lack an explicit CDI scope annotation. Since they
> are loaded/referenced programmatically, no error is thrown by the bean
> container explicitly, but rather they are just never resolved and effectively
> ignored.
> A simple fix is to add @Dependent CDI scope annotation (probably an oversight
> from the CDI-3 refactor).
> I'll open a GitHub PR with this fix next.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
