How do I make Tapestry notice my module?

[Xolani Nkosi]

I've written a module definition:

package org.foo.services;

import org.apache.tapestry5.ioc.ServiceBinder;

public class ServicesModule {
	public static void bind(ServiceBinder binder) {
		binder.bind(UserService.class, UserServiceImpl.class);
	}
}

When I start my web app up, I get this in the output from tapestry:

- Adding module definition for class org.apache.tapestry5.ioc.services.TapestryIOCModule
- Adding module definition for class org.apache.tapestry5.hibernate.HibernateModule
- Adding module definition for class org.apache.tapestry5.hibernate.HibernateCoreModule
- Adding module definition for class org.apache.tapestry5.upload.services.UploadModule
- Adding module definition for class org.apache.tapestry5.services.TapestryModule
- Adding module definition for class org.apache.tapestry5.internal.services.InternalModule

It hasn't found my ServicesModule - so where do I add this to get Tapestry to pick it up?

[Xolani Nkosi]

I appear to have answered my own question. As a note to framework authors, one problem with using convention over configuration, is if no-one explains the convention in the documentation, it can be hard to work out exactly what you need to do.

Anyway, it appears Tapestry looks for your module using the name you specified in your web.xml for the Tapestry filter. Yeah, wasn't expecting that...

So in my example, if I had:
<filter> <filter-name>testApp</filter-name> <filter-class>org.apache.tapestry5.TapestryFilter</filter-class> </filter> <filter-mapping> <filter-name>testApp</filter-name> <url-pattern>/*</url-pattern> </filter-mapping>
Then the module appears to be needed to be called:
org.foo.services.TestAppModule

Do that and it'll pick it up and load it