I'm still not sure what is happening here, but I no longer think the problem is with my Jetty configuration.
The exception is "ClassNotResolved", not "ClassNotFound" and is thrown from within my JDO stack. It happens when building a return class after the database query has completed. I haven't figured out the reason yet, but the JDO stack is not able to find the class when called from within the context of the #onSocketText callback. This works fine in other cases so there is definitely something happening in this case, I just think that it is more likely a misconfiguration of my JDO stack then Jetty. -Andrew On 14-05-16 09:40 PM, Andrew Eidsness wrote: > I'm having some class loading problems and I'm not sure if what I'm trying is > expected to work. I've read through > http://www.eclipse.org/jetty/documentation/current/jetty-classloading.html, > but am still not sure. > > The problem only happens for code that is running within my > WebSocketListener.onSocketText callback. I think this is > being loaded from the main Jetty class loader (because the stack starts with > at java.lang.Thread.run(Thread.java:744). > The class it can't find is deployed within a jar inside my .war file. > > The class is properly found when I make a simple method call (I call from the > callback to a static method on the > class). The problem happens when my JDO implementation tries to load the > class as part of a database request. > > If this type of deployment is expected to work then I'll look into other > components in the stack. > > -Andrew > _______________________________________________ > jetty-users mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/jetty-users > _______________________________________________ jetty-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/jetty-users
