Thanks Mark. The crucial piece that I missed was the filter-mapping for the to-be-included thing had to have
<dispatcher>INCLUDE</dispatcher> Now that it's all working, I updated the Github repo to be a demonstration of it all working, rather than a problem definition. - Paul On Tue, Jul 2, 2013 at 2:42 AM, Mark Thomas <ma...@apache.org> wrote: > On 02/07/2013 03:28, Paul Hammant wrote: > > Hi Mark, thanks for the reply. > > > > I've modified https://github.com/paul-hammant/servletDispatcherTest to > > include scripts to reproduce the problem, and to show the two web-apps > > working separately, but not in the getRequestDispatcher(..).include(..) > way. > > > > The scripts download an anointed version of Tomcat7, add > > the crossContext="true" attr to context.xml, and even copy the war files > > into the webapps/ folder. > > > > In the README.md, which Github kindly renders into HTML on the front page > > of the project, there's instructions to build/deploy, as well as what > URLs > > to click on to see the problem, as I see it. > > > > There are now three servlet-filters activated for different urls: > > > > /a/IOutputMyThreadID (class of same name) > > /a/AIncludingContentFromB (class of same name, extends > IOutputMyThreadID) > > /b/IAlsoOutputMyThreadID (class of same name) > > There is no Tomcat bug here. The bug is in the test case. > > Since the test is for Tomcat 7, see the following sections of the > Servlet 3.0 specification for an explanation: > - section 6.2.5 > - section 9.1 > > Mark > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >