[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

Wed Apr 18 07:26:19 EDT 2012

    [ https://issues.jboss.org/browse/CDI-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12685219#comment-12685219 ] 

Mark Struberg commented on CDI-123:
-----------------------------------

What's the status? I'm tempted to set this to "won't fix".
I've now used CDI in lots of real world projects and customers for more than 2 years and I know no single user who actually used it at the end of the day.

There were 2 customers who moved from Spring to CDI and originally intended to use it. But both ended up either using the Spring-CDI bridge or migrating parts to native annotation based CDI because re-doing all the configuration as CDI-xml was way too much work. Much more than just moving the Services to plain CDI. 

> 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: 1.1 (Proposed)
>
>
> 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: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira