Never mind. I renamed the TapestryFilter. Here are the docs that cover my issue:
From http://tapestry.apache.org/tapestry5/tapestry-core/guide/conf.html
Tapestry looks for a module builder class in the services package (under the root package). It capitalizes the <filter-name> and appends "Module". In the previous example, the module builder class would be org.example.myapp.services.AppModule. If such a class exists, it is added to the IoC Registry. It is not an error for your application to not have a module, though any non-trivial application will likely have one. On 6/7/07, Ben Tomasini <[EMAIL PROTECTED]> wrote:
I am working on a T5 application, and can't figure out how the AppModule is wired up to the IoC container in the quickstart example. In may application, I am working on extending TapestryFilter and overriding provideExtraModuleDefs to wire up the module in my web application, but am convinced there is a better way. What is the convention?
