[cdi-dev] CDI 1.2 Implementation

Romain Manni-Bucau rmannibucau at gmail.com
Tue Jan 28 07:36:15 EST 2014


I think it should still run on GlassFish to try to ensure
compatibility with previous version (at least). We all know
integration is where the most issues are.

Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau

2014-01-28 Jozef Hartinger <jharting at redhat.com>:
> Hi all,
> as many of you know already, Weld 2.2 is going to be the reference
> implementation of the upcoming maintenance release of the CDI specification.
> CDI is an EE specification. That implies that the CDI TCK which
> validates a CDI implementation has to be run against an EE container not
> just the CDI implementation itself (e.g. Weld Core).
> So far, both existing releases of CDI (1.0 and 1.1) were always part of
> a major Java EE release (6 and 7). It therefore made sense to require
> the CDI RI to run as part of the GlassFish application server since
> GlassFish is the RI for each recent Java EE version.
> However, with CDI 1.2 the situation is different. Since CDI 1.2 is not
> part of a major Java EE release, we see no reason to require the CDI 1.2
> RI to run specifically on GlassFish at the end of the maintenance
> release window. Instead, any Java EE 7 certified application server
> should be suitable. Therefore, we are going to use WildFly
> (http://wildfly.org/) as the runtime for CDI 1.2 RI and TCK.
> Note that this by no means defines which Java EE servers will or will
> not support CDI 1.2. This proposal only defines which Java EE server
> will be used at the end of the CDI 1.2 MR effort to validate the RI and
> the TCK.
> Regards,
> Jozef
> _______________________________________________
> cdi-dev mailing list
> cdi-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/cdi-dev

More information about the cdi-dev mailing list