[
https://issues.apache.org/jira/browse/WICKET-6330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15898081#comment-15898081
]
Martin Grigorov commented on WICKET-6330:
-----------------------------------------
OK. I see.
I was supposed to use 'mvn jetty:run' from the command line.
Now I am able to reproduce the problem.
I am afraid this is a Jetty + Maven configuration issue and Wicket cannot help
you with it.
Either deploy your app in a standalone web container or ask in Maven/Jetty
forums for help.
> Could not resolve class [net.sf.wicketautodao.model.AutoDaoFinder]
> ------------------------------------------------------------------
>
> Key: WICKET-6330
> URL: https://issues.apache.org/jira/browse/WICKET-6330
> Project: Wicket
> Issue Type: Bug
> Components: wicket, wicket-native-websocket
> Affects Versions: 7.6.0
> Environment: Jetty 9.2.6 ; wicket 7.6.0 ; spring 4.2.4 ;
> javax.servlet 3.0.1
> Reporter: Mikhail Kim
> Assignee: Martin Grigorov
> Attachments: log.txt, quickStartApp.zip
>
>
> Hello!
> When I am refreshing page with native websocket I get the next message:
> java.lang.ClassNotFoundException: net.sf.wicketautodao.model.AutoDaoFinder
> at
> org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
> ~[plexus-classworlds-2.5.2.jar:na]
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271)
> ~[plexus-classworlds-2.5.2.jar:na]
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:247)
> ~[plexus-classworlds-2.5.2.jar:na]
> at
> org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239)
> ~[plexus-classworlds-2.5.2.jar:na]
> at java.lang.Class.forName0(Native Method) ~[na:1.8.0_112]
> at java.lang.Class.forName(Class.java:348) ~[na:1.8.0_112]
> at
> org.apache.wicket.application.AbstractClassResolver.resolveClass(AbstractClassResolver.java:101)
> ~[wicket-core-7.6.0.jar:7.6.0]
> at
> org.apache.wicket.core.util.lang.WicketObjects.resolveClass(WicketObjects.java:71)
> ~[wicket-core-7.6.0.jar:7.6.0]
> at
> org.apache.wicket.proxy.LazyInitProxyFactory$ProxyReplacement.readResolve(LazyInitProxyFactory.java:262)
> [wicket-ioc-7.6.0.jar:7.6.0]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> ~[na:1.8.0_112]
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> ~[na:1.8.0_112]
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ~[na:1.8.0_112]
> at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_112]
> at
> java.io.ObjectStreamClass.invokeReadResolve(ObjectStreamClass.java:1148)
> [na:1.8.0_112]
> Why are you using non-standard classloader in AbstractClassResolver.java:101
> ?
> full log attached in log.txt
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
