In your web.xml, please check you are using TapestrySpringFilter (instead of
TapestryFilter):
app
org.apache.tapestry5.spring.TapestrySpringFilter
Shing
From: Borko Djurovic
To: users@tapestry.apache.org
Sent: Tuesday, September
OK, figured it out. I didn't realise that TapIOC loads ANY modules that
it finds (in the classpath).
Removing the tapestry-spring.jar fixed the problem.
Is there a way to explicitly prevent TapIOC loading a module, so that I
can continue to have SpringModule on the classpath, but without it being
I've managed to get a little further with this by defining a service
builder method for ApplicationContext in:
com.howardlewisship.tapx.templating.services.TemplateModule
like this:
public static ApplicationContext build() {
TapestryApplicationContext tac = new TapestryApplicationCon
