On Tuesday, 6 January 2015, 14:42, Werner Keil <[email protected]> wrote:
>As Java CDI 2 and EE 8 (some or all of its components will require Java SE 8
>as prerequisite) have just started, none of them even produced an EDR, I would
>also prefer starting with Java (EE) 7 for now.
+1
Also for CDI there are compatible CDI-1.0 and CDI-1.0 impls already which
people can use if they need SE7. For javaconfig we don't have such. We could do
a javaconfig-2.0 which is backward compat and supports Java8 styles.
> that's not going to be final till 2016/17.
Hah, 2018/19 might even be too early...
As an example: How many enterprise ready EE7 servers do you know?
There is only a single one: TMax JEUS (only common in some asian countries).
All others (Glassfish4, Wildfly8) are *explictly* not intended for enterprise
grade production scenarios still. All other vendors don't even have an EE7 impl
yet.
So maybe we will see EE7 (SEVEN that is!) in big companies starting with this
year. This makes it 3 years from spec ready to production ready. Now the EE8
spec is targeted for 2016 and probably might get stretched to 2017. Do the math
yourself ;)
LieGrue,
strub
