Hi,
On Fri, Apr 25, 2014 at 3:12 PM, Dünnenberger, Hanspeter <
hanspeter.duennenberger_at_credit-suisse.com> wrote:
> Unfortunately it takes years to get JEE container updated [...]
>
> Because WLS 12 with JEE6 only contains JSF 2.1 we usually have to deliver
> newer
> JSF RI version as part of the application (updating the container is to
> complicated).
>
I know it's the reality for some and this discussion is primarily about
which JDK is practical for JSF.next, but I still wonder how companies can
get into the situation where JSF as part of the application can be updated
whenever this is deemed necessary but updating the JDK and AS has to take
years.
At m4n.nl where I worked before and now at zeef.com the deliverable after
each sprint is a unit consisting of the JDK + AS + application archive,
which is then deployed to a virtual server for production.
I always found it a weird idea that people can upgrade some parts of their
stack but not others and thereby causing some unbalance. E.g. the very
latest bleeding edge version of JSF and CDI, but a very old Servlet version
and an ancient JDK.
Kind regards,
Arjan Tijms