Romain is right. The cleanup now happens if another request is done. Otherwise the session will expire anyway.
We _might_ add this again if there is a real need. We could e.g. keep track of those Conversations via WeakReferences. But we would need to think a bit about if it’s worth it. If serialisation kicks in then all those things get a bit more complicated… LieGrue, strub > Am 04.12.2015 um 14:54 schrieb Romain Manni-Bucau <[email protected]>: > > Hi Emily, > > conversations are now in the session so when the session is evicted > conversations are so no need of our own scheduler. > > > Romain Manni-Bucau > @rmannibucau <https://twitter.com/rmannibucau> | Blog > <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber > <http://www.tomitribe.com> > > 2015-12-04 14:53 GMT+01:00 Emily Jiang <[email protected]>: > >> Hi Mark, >> >> I noticed this https://issues.apache.org/jira/browse/OWB-1050. Am I >> correct >> to say that this jira removes the support for >> org.apache.webbeans.conversation.Conversation.periodicDelay, which means >> from OWB 1.6, this property does not work any more? If yes, can you please >> explain why you need to remove this facility? >> >> -- >> Thanks >> Emily >> ================= >> Emily Jiang >> [email protected] >>
