Hi there,
just to let you know, I now figured out what the problem was: I was
still using T5Components 0.5.10, and I suppose that refered to
org.apache.tapestry.internal.services.ClassNameLocator. Updating to T5C
0.5.11 solved this problem.
Regards,
Tobias
Tobias Wehrum schrieb:
It's tapestry-ioc-5.0.11.jar. Just downloaded via maven:
<dependency>
<groupId>org.apache.tapestry</groupId>
<artifactId>tapestry-ioc</artifactId>
<version>5.0.11</version>
</dependency>
Howard Lewis Ship schrieb:
Check your version of tapestry-ioc. ClassNameLocator moved there in
5.0.11.
On Fri, Mar 14, 2008 at 5:49 AM, Tobias Wehrum <[EMAIL PROTECTED]>
wrote:
Hi all,
after updating to Tapestry 5.0.11, I get the following error:
Exception in thread "main" java.lang.NoClassDefFoundError:
org/apache/tapestry/internal/services/ClassNameLocator
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Unknown Source)
at java.lang.Class.privateGetPublicMethods(Unknown Source)
at java.lang.Class.getMethods(Unknown Source)
at
org.apache.tapestry.ioc.internal.DefaultModuleDefImpl.grind(DefaultModuleDefImpl.java:137)
at
org.apache.tapestry.ioc.internal.DefaultModuleDefImpl.<init>(DefaultModuleDefImpl.java:106)
at
org.apache.tapestry.ioc.RegistryBuilder.add(RegistryBuilder.java:112)
at
org.apache.tapestry.ioc.RegistryBuilder.add(RegistryBuilder.java:131)
at
org.apache.tapestry.ioc.IOCUtilities.addModulesInList(IOCUtilities.java:122)
at
org.apache.tapestry.ioc.IOCUtilities.addModulesInManifest(IOCUtilities.java:106)
at
org.apache.tapestry.ioc.IOCUtilities.addDefaultModules(IOCUtilities.java:78)
at
org.apache.tapestry.internal.TapestryAppInitializer.<init>(TapestryAppInitializer.java:75)
at org.apache.tapestry.TapestryFilter.init(TapestryFilter.java:72)
at
org.mortbay.jetty.servlet.FilterHolder.start(FilterHolder.java:71)
at
org.mortbay.jetty.servlet.WebApplicationHandler.initializeServlets(WebApplicationHandler.java:310)
at
org.mortbay.jetty.servlet.WebApplicationContext.doStart(WebApplicationContext.java:509)
at org.mortbay.util.Container.start(Container.java:72)
at org.mortbay.http.HttpServer.doStart(HttpServer.java:708)
at org.mortbay.util.Container.start(Container.java:72)
at dw.protask.JettyServer.main(JettyServer.java:46)
I don't use tapestry-hibernate. When I include it, the exception
vanishes and my server loads correctly. (But a whole lot of others
occurs on the sites, presumably due to missing hibernate
configuration,
so this is not even usable as work-around.)
Regards,
Tobias Wehrum
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
