After reading through the Jetty source code I discovered that there is now a new dispatcher type called ASYNC. I added <dispatcher>ASYNC</dispatcher> to the filter-mapping entry and that took care of it.
I am using jetty 7.1.5. I have a servlet Filter that acts as the basis of my web framework. In my > web.xml I have specified that I want the filter to also act as a FORWARD > dispatcher. This is required for another feature in my framework. > Now I am trying to add support for asynchronous continuations. The problem > I've come across is that when the continuation is resumed (or when the > continuation expires) jetty is never dispatching the "resumed" request to > my filter. If I write a servlet, then it will get the "resumed" request. And > if I remove the <dispatcher>FORWARD</dispatcher>and > <dispatcher>REQUEST</dispatcher> from my web.xml file then the filter does > get the "resumed" request. Is there anyway that I can have the "resumed" > request dispatched to my filter even with FORWARD dispatching enabled? > After playing around a bit more, the problem arises whenever I have any > <dispatcher> entries. Even if there is only a > <dispatcher>REQUEST</dispatcher> entry. In order for it to work, there must > be no dispatcher entries at all. ÂIt this by design or have I stumbled on a > bug?
_______________________________________________ jetty-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/jetty-users
