You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltaspike.apache.org by "Mark Struberg (JIRA)" <ji...@apache.org> on 2013/05/24 08:34:20 UTC

[jira] [Resolved] (DELTASPIKE-208) activateGlobalAlternatives is broken

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

Mark Struberg resolved DELTASPIKE-208.
--------------------------------------

    Resolution: Fixed
    
> activateGlobalAlternatives is broken
> ------------------------------------
>
>                 Key: DELTASPIKE-208
>                 URL: https://issues.apache.org/jira/browse/DELTASPIKE-208
>             Project: DeltaSpike
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.2-incubating
>            Reporter: Mark Struberg
>            Assignee: Mark Struberg
>             Fix For: 0.4-incubating
>
>
> for OWB:
> a.) We shall not need to do anything special for OWB at all. OWB by default comes without BDA enabled. If people have BDA enabled in their OWB installation, then they can _easily_ switch it off again via a simple property. There is really no need to do something special for OWB.
> b.) replacing the AnnotatedType with a completely different return Type screws up the CDI container. It's really not expected and I'm not sure if this is allowed at all.
> c.) by replacing the target type, you end up not scanning one of this class at all, effectively disabling Extension processing for it.
> for Weld:
> instead of introducing our own properties we shall scan the beans.xml and act accordingly.
> in general: mixing this complicated topic with the @Exclude extension is highly confusing.

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