Hi Joakim, Thanks for the quick reply, however I am not sure if I quite explained my need in enough detail...
We need to do this after Jetty has already been configured and started. > The class MUST be a class accessible via a JAR or FileSystem (no dynamic > classes or purely runtime classes supported). > This is because the only way we can scan for Annotations is via the ASM > library. The class is in a Jar file which we have loaded using our custom classloader named org.exist.start.EXistClassLoader. I am not sure how Jetty would know about this class loader? Do we need to tell Jetty about it somehow? > If these classes are on the Server / System classpath, then the > `org.eclipse.jetty.server.webapp.ContainerIncludeJarPattern` context > attribute can be modified (hint: it's a regex) to include the server jars (of > filesystem paths) that have your classes that you are interested in. > The classes are NOT on the Server or the System classpath, they are loaded on-demand at runtime via our EXistClassLoader. So I don't think changing `ContainerIncludeJarPattern` will help here. Does that make more sense now? -- Adam Retter skype: adam.retter tweet: adamretter http://www.adamretter.org.uk _______________________________________________ jetty-users mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jetty-users
