I would just like to note that we definitely support the idea of a Config JSR. And we would provide strong EG representation, and help with RI/TCK. However we are unable to take a lead role in it right now, due to having many other things going on. On 5 Sep 2014, at 15:43, Werner Keil <werner.keil(a)gmail.com&gt; wrote: > You got a point, but so far both Oracle and Red Hat dismissed the idea of a separate Config JSR. Anatole was in touch with both of them and either their resources or interest seemed to lack. > > It is quite a shamble, that e.g. JSR 107 already went down the path of a completely separate Config sub-system (https://github.com/jsr107/jsr107spec/tree/master/src/main/java/javax/cach...) while pruning other much more importent (especially for true EE 8 value) features like Transaction Support in line with JTA, etc. > > If CDI2 needed a config sub-system, too, we better avoid their mistake or (for EE 8 since it is considered for inclusion) look at ways this may work together in some unified way. > Whether it's a separate JSR or "Module" of CDI 2 I don't really care, but we must not fall into the same "Not invented Here" trap as Java SE did with all its redundant and bloated features like JavaFX having its own Date/Time same as java.util.Date (which aside from JSR 236 also is the only one relevant to EE, JDBC, etc.) or the extra package java.time. > > JCache already went in the wrong direction here, as it is final there is probably not a lot to do, but do we really want to end up with > - JCache-config > - CDI-config > - MVC-config > ... > > ??;-O > > Werner > > On Fri, Sep 5, 2014 at 4:24 PM, <cdi-dev-request(a)lists.jboss.org&gt; wrote: > Send cdi-dev mailing list submissions to > cdi-dev(a)lists.jboss.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.jboss.org/mailman/listinfo/cdi-dev > or, via email, send a message with subject or body 'help' to > cdi-dev-request(a)lists.jboss.org > > You can reach the person managing the list at > cdi-dev-owner(a)lists.jboss.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of cdi-dev digest..." > > > Today's Topics: > > 1. [JBoss JIRA] (CDI-4) Need a way to provide ordering for Event > observers (Martin Kouba (JIRA)) > 2. Re: cdi-dev Digest, Vol 46, Issue 16 (Werner Keil) > 3. Re: With the end of Java Config... (John D. Ament) > > ------------------------------ > > Message: 3 > Date: Fri, 5 Sep 2014 10:24:37 -0400 > From: "John D. Ament" <john.d.ament(a)gmail.com&gt; > Subject: Re: [cdi-dev] With the end of Java Config... > To: Antonio Goncalves <antonio.goncalves(a)gmail.com&gt; > Cc: cdi-dev <cdi-dev(a)lists.jboss.org&gt; > Message-ID: > <CAOqetn8UrpdWEFV8LJJ57hJ+z-iAFNjEEzyqsfPXFUQutuqT8A(a)mail.gmail.com&gt; > Content-Type: text/plain; charset="utf-8" > > Agreed w/ Antonio. JAX-RS did the right thing by making MVC a separate > spec. While we can provide a way to wire up beans externally w/ an XML > DSL, I don't think we should get into the business of config properties,etc. > > > On Fri, Sep 5, 2014 at 10:08 AM, Antonio Goncalves < > antonio.goncalves(a)gmail.com&gt; wrote: > > > One wise man* once said "EJB was a hype specification, we added too many > > things to it, it became bloated. The next hype specifications are JAX-RS > > and CDI, careful with them" > > > > Either we get this idea of "parts" right, or CDI will endup being bloated. > > > > Antonio > > > > > > *David Blevin > > > > > > On Fri, Sep 5, 2014 at 3:28 PM, Antoine Sabot-Durand < > > antoine(a)sabot-durand.net&gt; wrote: > > > >> Hi all, > >> > >> You may have followed the rise and fall of the Java Config JSR ( > >> http://javaeeconfig.blogspot.ch/2014/09/no-java-ee-configuration-for-ee8-... > >> ). > >> Anatole in CC was leading this initiative and I proposed him to join us > >> and explore if some part of his late-JSR could be done in CDI. > >> > >> I?m mainly thinking of https://issues.jboss.org/browse/CDI-123 or > >> related solution. If we achieve to have a majority of specs to integrate > >> with CDI, our configuration solution would therefore become a configuration > >> system for all spec based on CDI 2.0. > >> > >> Antoine > >> > >> > >> > >> _______________________________________________ > >> cdi-dev mailing list > >> cdi-dev(a)lists.jboss.org > >> https://lists.jboss.org/mailman/listinfo/cdi-dev > >> > >> Note that for all code provided on this list, the provider licenses the > >> code under the Apache License, Version 2 ( > >> http://www.apache.org/licenses/LICENSE-2.0.html). For all other ideas > >> provided on this list, the provider waives all patent and other > >> intellectual property rights inherent in such information. > >> > > > > > > > > -- > > Antonio Goncalves > > Software architect, Java Champion and Pluralsight author > > > > Web site <http://www.antoniogoncalves.org> | Twitter > > <http://twitter.com/agoncal> | LinkedIn > > <http://www.linkedin.com/in/agoncal> | Pluralsight > > <http://pluralsight.com/training/Authors/Details/antonio-goncalves> | Paris > > JUG <http://www.parisjug.org> | Devoxx France <http://www.devoxx.fr> > > > > _______________________________________________ > > cdi-dev mailing list > > cdi-dev(a)lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/cdi-dev > > > > Note that for all code provided on this list, the provider licenses the > > code under the Apache License, Version 2 ( > > http://www.apache.org/licenses/LICENSE-2.0.html). For all other ideas > > provided on this list, the provider waives all patent and other > > intellectual property rights inherent in such information. > > >