I have created a filter and it uses ContextualHttpServletRequest to work with Seam components inside the filter.
When I try to create a long running conversation via Seam UI, <s:link propagation="begin"/>, ContextualHttpServletRequest also creates an empty long running conversation on top of the long running conversation created by s:link tag. Thus there are two long running conversation show up in Seam debug page.
To validate the observation, I have create an empty process() method inside ContextualHttpServletRequest to make sure the empty long running conversation is not caused by my codes.
Does anyone have any idea on this? Thanks.
