ExpiredFlowCleanupFilter is removed?

amy

Is there a replacement for this?

Thanks,
Alex

There is conversation invalidation after completion--in PR5 after a conversation ended all conversation continuations would still hang around; now they're automatically cleaned up when a conversation ends.

There is currently no out-of-the box conversation expiry feature that works with the new repository infrastructure; however.  There is a JIRA issue on it though as an enhancement.

Keith

Hi, Keith,

Would you mind pointing me to the issue for this?

Thanks,

Rob

Rob,
It's intended to be this one:
proj.../browse/SWF-10
We need to update the description to reflect the recent work

Thanks, Keith. I'm currently looking for ways to expire abandoned flows, hence my interest. Is that to be addressed in this issue?

Rob

It is but it's not as high priority as some other issues for RC2, such as JSF improvements.  Any assistance you can provide here would be greatly appreciated.  Basically, we see expiry needing to happen within the FlowExecutionRepository subsystem.  Probably driven on a per-request (sweeper) manner, but possibly also via a reaper thread managed as a JMX MBean.
Keith

Is there any method left in Webflow 2 that allows intercepting of flow expiring?
The issue specifies implementing a custom ConversationManager but it seems difficult to do because you would need to intercept conversation transitions to update some timer...