I wonder whether this behavior is defined somewhere, i.e. if all EJB
implementations must support "failover" between minor versions (e.g. EJB
3.0 and 3.2), in other words the passivation mechanism may not change.
This would mean that an EJB app might be deployed to a "cluster" of
mixed Java EE 6 and Java EE 7 app servers - seems to me like an
extremely risky experiment.
Martin
Dne 9.10.2015 v 11:42 Emily Jiang napsal(a):
I am investigating the HttpSession failover for SessionScoped or
ConversationScoped beans. I think it is not easy to failover from the
CDI 1.0 impl to CDI1.2 impl, as the bean proxies instead of the raw bean
was serialised and the proxies are different between cdi 1.0 and cdi
1.2. Has anyone have any thoughts on this? If not possible, this is a
big limitation for CDI as EJB container has no such limitation.
--
Thanks
Emily
=================
Emily Jiang
ejiang(a)apache.org <mailto:ejiang@apache.org>
_______________________________________________
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.
--
Martin Kouba
Software Engineer
Red Hat, Czech Republic