[cdi-dev] [JBoss JIRA] (CDI-123) Using Seam XML extension for CDI and Candi XML as a guide, let's add the ability to do XML config back into the specification

[Pete Muir (JIRA)]

     [ https://issues.jboss.org/browse/CDI-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pete Muir updated CDI-123:
--------------------------

    Fix Version/s: TBD
                       (was: 1.1 (Proposed))


Discussed in EG meeting, there is not really consensus in the community about the right way to resolve this, and we're running out of time to add new large features to CDI 1.1
                
> Using Seam XML extension for CDI and Candi XML as a guide, let's add the ability to do XML config back into the specification
> -----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CDI-123
>                 URL: https://issues.jboss.org/browse/CDI-123
>             Project: CDI Specification Issues
>          Issue Type: Feature Request
>          Components: Concepts
>    Affects Versions: 1.0
>            Reporter: Richard Hightower
>             Fix For: TBD
>
>
> Using Seam's CDI XML extension for CDI and Candi XML as a guide, let's add the ability to do XML config back into the specification.
> Annotations and Alternatives should always be the first line of offense for doing injection, decoration and interception. However, there are times when you want to configure things that don't fit well into this model. This is also useful for testing.
> This is not to give up type safeness via annotations, but to have some additional flexibility.

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