You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltaspike.apache.org by "John D. Ament (JIRA)" <ji...@apache.org> on 2013/03/26 14:45:18 UTC
[jira] [Resolved] (DELTASPIKE-105) remove workarounds for weld
[ https://issues.apache.org/jira/browse/DELTASPIKE-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John D. Ament resolved DELTASPIKE-105.
--------------------------------------
Resolution: Won't Fix
Consensus was that the work arounds are needed for older Weld versions.
> remove workarounds for weld
> ---------------------------
>
> Key: DELTASPIKE-105
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-105
> Project: DeltaSpike
> Issue Type: Sub-task
> Components: CdiControl
> Affects Versions: 0.2-incubating
> Reporter: Gerhard Petracek
> Assignee: Ales Justin
> Fix For: 0.4-incubating
>
>
> currently we have 2 workarounds which need to be removed as soon as we have a released version of weld which fixes the following issues:
> #1 the application scope doesn't get restarted autom. after it is invalidated and it can't be started manually (reason: IsolatedStaticSingleton.object is null after calling applicationContext#invalidate and causes a NPE as soon as the scope gets accessed again)
> the workaround is in ContextController#stopApplicationScope
> #2 AbstractSharedContext#isActive always returns true
> the workaround is in ContainerCtrlTckTest#reStartContexts
> ContainerCtrlTckTest#reStartContexts has to pass without workarounds
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira