An exception at jetty starts up while using classNameLocator

[dh ning]

Hi,

I got an exception when Jetty starts up after my maven repository updates to
the latest tapestry 5.0.15-snapshot(I haven't update my repository for
about 3 weeks), the latest 5.0.14-snapshot can't work too. The exception is:

[ERROR] ClassNameLocator Construction of service ClassNameLocator failed:
Error invoking constructor
org.apache.tapestry5.ioc.internal.services.ClassNameLocatorImpl(ClasspathURLConverter)
(at ClassNameLocatorImpl.java:61) (for service 'ClassNameLocator'):
Exception constructing service 'Alias': Construction of service 'Alias' has
failed due to recursion: the service depends on itself in some way. Please
check org.apache.tapestry5.services.TapestryModule.buildAlias(Logger,
String, AliasManager, Collection) (at TapestryModule.java:207) for
references to another service that is itself dependent on service 'Alias'.

I find the cause is the usage of ClassNameLocator in my AppModule.java. It
is very simple.

public class AppModule
{

    public static void contributeTypeCoercer(
            Configuration<CoercionTuple> configuration,
            final ClassNameLocator classNameLocator) {
        classNameLocator.locateClassNames("com.mycompany.entities");
        .... other codes
    }
}

If I comment classNameLocator.locateClassNames("com.mycompany.entities"),
then everything works and Jetty starts up.

Please help on solving the problem. It blocks me for several days. Thanks.


DH