You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltaspike.apache.org by "Thomas Andraschko (JIRA)" <ji...@apache.org> on 2014/02/26 10:23:20 UTC

[jira] [Assigned] (DELTASPIKE-529) DeltaSpikeExceptionHandler construction issue in non EE

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

Thomas Andraschko reassigned DELTASPIKE-529:
--------------------------------------------

    Assignee: Thomas Andraschko

> DeltaSpikeExceptionHandler construction issue in non EE
> -------------------------------------------------------
>
>                 Key: DELTASPIKE-529
>                 URL: https://issues.apache.org/jira/browse/DELTASPIKE-529
>             Project: DeltaSpike
>          Issue Type: Bug
>          Components: JSF-Module
>    Affects Versions: 0.5, 0.6
>         Environment: Tomcat
>            Reporter: Bryn Cooke
>            Assignee: Thomas Andraschko
>             Fix For: 0.6
>
>
> In non EE environments you may be using Weld Servlet to initialize CDI.
> However because of JSF zeroconfig you cannot guarantee that weld servlet will be started before JSF.
> During JSF startup DeltaSpikeExceptionHandler is created and exceptionQualifier is populated, but it throws an exception because the following will only work once the CDI container is started:
> this.exceptionQualifier = AnnotationInstanceProvider.of(
>                     BeanProvider.getContextualReference(JsfModuleConfig.class).getExceptionQualifier());
> Recommend either not caching the exceptionQualifier, or moving the initialization to the handle() method if null.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)