[cdi-dev] [JBoss JIRA] Commented: (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

[Mark Struberg]

Actually I would go even further:

If there is a way to implement a feature in a portable extension, then there must be a _very_ good argument to even think about moving it to the CDI core spec. 

Imo the CDI spec itself should be as compact as possible. WDYT?

LieGrue,
strub

--- On Sun, 5/1/11, Pete Muir <pmuir at redhat.com> wrote:

> From: Pete Muir <pmuir at redhat.com>
> Subject: Re: [cdi-dev] [JBoss JIRA] Commented: (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
> To: "Mark Struberg (JIRA)" <jira-events at lists.jboss.org>
> Cc: cdi-dev at lists.jboss.org
> Date: Sunday, May 1, 2011, 5:59 PM
> Mark you raise a really good point
> here which is that when considering a feature a big element
> of whether we should give it priority for adding to the spec
> is whether it is possible to do it in a totally portable
> fashion already in an extension. If it is, then it's
> priority must necessarily be lower.
> 
> On 1 May 2011, at 13:47, Mark Struberg (JIRA) wrote:
> 
> > 
> >    [ https://issues.jboss.org/browse/CDI-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12599308#comment-12599308
> ] 
> > 
> > Mark Struberg commented on CDI-123:
> > -----------------------------------
> > 
> > Actually this has been in the spec originally and got
> dropped later. 
> > There are multiple reasons for dropping it:
> > 
> > a) it would bloat the spec (would take at least 10
> pages to define all that stuff unambiguous)
> > 
> > b) back then there was a BIG discussion about the
> style. Some wanted it 'modern', others wanted it EJB like. 
> > 
> > c) Seam XML or any other configuration Extension is
> portable anyway.
> > 
> > d) In a Cluster/Cloud environment, you maybe like to
> configure your beans via the Database? So we could not
> satisfy all the needs anyway.
> > 
> > 
> >> 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
> >>       
>    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.
> > For more information on JIRA, see: http://www.atlassian.com/software/jira
> > _______________________________________________
> > cdi-dev mailing list
> > cdi-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/cdi-dev
> 
> 
> _______________________________________________
> cdi-dev mailing list
> cdi-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/cdi-dev
>