Re: [cdi-tck] [cdi-dev] session destroyed event
by Tomas Remes
Hi,
I think the destroy event is triggered at the end of the request and not immediately if I understand correctly. The spec states:
"The session context is destroyed when the HTTPSession times out, after all
HttpSessionListener s have been called, and at the very end of any request in which
invalidate() was called, after all filters and ServletRequestListener s have been called."
Please let's move TCK related topics to cdi-tck mailing list.
Thank's
Tom
----- Original Message -----
From: "Romain Manni-Bucau" <rmannibucau(a)gmail.com>
To: cdi-dev(a)lists.jboss.org
Sent: Tuesday, December 23, 2014 8:58:16 PM
Subject: [cdi-dev] session destroyed event
Hi
why org.jboss.cdi.tck.tests.context.session.event.Servlet#doGet ensures
destroyed == observer.getDestroyedSessionCount().get()
For me invalidate call should trigger the destroy event: you can
create N session in a single requests
Romain Manni-Bucau
@rmannibucau
http://www.tomitribe.com
http://rmannibucau.wordpress.com
https://github.com/rmannibucau
_______________________________________________
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.
9 years, 4 months
2.0.0.Alpha1 release
by Tomas Remes
Hi,
CDI TCK 2.0.0.Alpha1 was released. Note that this still corresponds to CDI 1.2 because CDI 2.0 is on the way. There was added couple of new tests in this release so you can give it a try.
Thank's
--
Tomas Remes
9 years, 4 months