[
https://issues.apache.org/jira/browse/DELTASPIKE-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17108218#comment-17108218
]
ASF subversion and git services commented on DELTASPIKE-1408:
-------------------------------------------------------------
Commit 19606ca588233676a6db64cb61b81f382014181d in deltaspike's branch
refs/heads/master from Mark Struberg
[ https://gitbox.apache.org/repos/asf?p=deltaspike.git;h=19606ca ]
DELTASPIKE-1408 in some situations CDI.current() doesn't work in Weld3
So we try a fallback onto CDI-1.0 tricks to resolve the BeanManager.
> Some Weld versions fail on CDI.current() depending on the ClassLoader setup
> ---------------------------------------------------------------------------
>
> Key: DELTASPIKE-1408
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1408
> Project: DeltaSpike
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Core
> Affects Versions: 1.9.3
> Reporter: Mark Struberg
> Assignee: Mark Struberg
> Priority: Major
> Fix For: 1.9.4
>
>
> Weld 3.1.3.Final and others blow up with an internal Exception when calling
> {{CDI.current()}} in some situations (ClassLoader, boot order, not sure yet).
> What we can rather easily do is to fallback to our classic CDI-1.0 behaviour
> in this case.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
