@Gerhard: that's what I thought @Dimitry: maybe check logs, you should see beans persisted accross the cluster after each request Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau
2014-03-05 16:43 GMT+01:00 Gerhard Petracek <[email protected]>: > @romain: > instances of JsfWindowContext are stored in > EditableWindowContextManagerProxy which is (cdi-)session-scoped. > (esp. to benefit from session replication,...) > > regards, > gerhard > > > > 2014-02-12 12:36 GMT+01:00 Romain Manni-Bucau <[email protected]>: > >> sorry, I don't get the question. If session beans works it is not >> tomee related but surely codi which shouldn't hit session from its >> storage. >> Romain Manni-Bucau >> Twitter: @rmannibucau >> Blog: http://rmannibucau.wordpress.com/ >> LinkedIn: http://fr.linkedin.com/in/rmannibucau >> Github: https://github.com/rmannibucau >> >> >> >> 2014-02-12 12:34 GMT+01:00 <[email protected]>: >> > Session Beans are replicated perfectly. I have tested my app earlier >> with TomEE 1.6.0-Snapshot and tomcat 7 and same CODI version. It was >> working fine. Could you please check if it is not a Tomee issue? >> > >> > >> > -----Ursprüngliche Nachricht----- >> > Von: Romain Manni-Bucau [mailto:[email protected]] >> > Gesendet: Mittwoch, 12. Februar 2014 12:12 >> > An: [email protected] >> > Betreff: Re: CODI WindowScoped Beans replication >> > >> > does it reproduce with session bean (without codi?)? if no maybe ask >> codi list Romain Manni-Bucau >> > >> > >> > >>
