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