I think that the rationale behind upgrading to CDI 1.1 is the support of
the conversational scope right in the spec.
Right now it is plumbed using seam-conversation-spi along with the
appropriate seam-conversation-{weld,owb,candi} container integration
module. The point is that seam-conversation is somewhat outdated and seems
abandoned (no new releases since version 3.0 in January 2012). It will not
work with openwebbeans >=1.1.4 nor will it work with tomee >=1.5.0 leaving
the user with the only option - weld 1.1.x. Don't be affraid of cdi 1.1 not
being implemented in containers, one can always settle for custom cdi
integration, deployed as part of web application - both weld and owb are
fitted with appropriate listeners that bootstrap embedded cdi container.
Besides, cdi 1.1 implementations are around the corner - Weld 2.0.0.Final
got released on 24 April, OWB guys declare that it will be pretty
straightforward to support CDI 1.1 after the refactorings that they had
done to OWB 1.2. I understand that upgrading CDI impl in containers already
supporting it is not an option, but by the time wicket 7 RCs start rolling,
both wildfly (jboss 8) and glassfish 4 reach GA (both use weld).regz, /dd 2013/5/6 Emond Papegaaij <[email protected]> > Hi all, > > I noticed the TODO for Wicket 7 to upgrade the CDI dependency > to 1.1. I think it's better to pospone this upgrade to Wicket 8. > CDI 1.1 is part of JEE 7, for which the spec only has been > approved last week. Containers will need some time to > implement the spec, for example wildFly (formerly JBoss) 8 is > expected to be released in November and Glassfish somewhere > this summer. Upgrading CDI in a container like Glassfish 3.2 or > JBoss 7 often is not option, so I think it's probably better not to > upgrade wicket-cdi before containers supporting CDI 1.1 are > available. > > Best regards, > Emond > -- /* Spelin donut mader if iz ina coment */
