[jira] [Resolved] (DELTASPIKE-1468) AuditProvider (PrincipalProvider/TimestampsProvider) not working

2024-01-10 Thread Thomas Andraschko (Jira)


 [ 
https://issues.apache.org/jira/browse/DELTASPIKE-1468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Thomas Andraschko resolved DELTASPIKE-1468.
---
Resolution: Fixed

> 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)


[jira] [Updated] (DELTASPIKE-1468) AuditProvider (PrincipalProvider/TimestampsProvider) not working

2024-01-10 Thread Thomas Andraschko (Jira)


 [ 
https://issues.apache.org/jira/browse/DELTASPIKE-1468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Thomas Andraschko updated DELTASPIKE-1468:
--
Fix Version/s: 2.0

> 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
> Fix For: 2.0
>
>
> 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)


[jira] [Commented] (DELTASPIKE-1468) AuditProvider (PrincipalProvider/TimestampsProvider) not working

2024-01-10 Thread ASF subversion and git services (Jira)


[ 
https://issues.apache.org/jira/browse/DELTASPIKE-1468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)


Re: [PR] add explicit dependent scope to PrincipalProvider and TimestampsProvider beans [deltaspike]

2024-01-10 Thread via GitHub


tandraschko merged PR #138:
URL: https://github.com/apache/deltaspike/pull/138


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@deltaspike.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



[jira] [Created] (DELTASPIKE-1468) AuditProvider (PrincipalProvider/TimestampsProvider) not working

2024-01-10 Thread Phillip Ross (Jira)
Phillip Ross created DELTASPIKE-1468:


 Summary: 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


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)