deltaspike-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gerhard Petracek (JIRA)" <>
Subject [jira] [Comment Edited] (DELTASPIKE-208) activateGlobalAlternatives is broken
Date Fri, 06 Jul 2012 21:30:34 GMT


Gerhard Petracek edited comment on DELTASPIKE-208 at 7/6/12 9:29 PM:

original discussion:
since you don't use beans.xml for it, you also need it for owb to keep an application portable.
and with cdi 1.1 you >can< move the config used in the properties file to the beans.xml
and the behaviour is the same.
however, it's correct that it isn't compatible with more complex extensions which handle an
alternative bean differently. so it needs to be documented.
but it works pretty fine for a lot of use-cases e.g. for custom implementations of config
beans (even with old versions of weld).
      was (Author: gpetracek):
    original discussion:
> activateGlobalAlternatives is broken
> ------------------------------------
>                 Key: DELTASPIKE-208
>                 URL:
>             Project: DeltaSpike
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.2-incubating
>            Reporter: Mark Struberg
>            Assignee: Mark Struberg
>             Fix For: 0.3-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:!default.jspa
For more information on JIRA, see:


View raw message