: Actually, I meant to say I have my Tokenizer jars in solr/lib. : I have the jars that my Tokenizer jars depend in lib/ext, : as I wanted them to be loaded only once per container : due to their internal description. Bad idea?
unless there is something *really* hinky about those dependencies, i wouldn't worry about it -- just put them in solr/lib as well (or sharedLib if you use a solr.xml file) : > This error can be fixed by putting another set of SLF4J jars : > in example/lib/ext, but I don't understand why. In generaly what you are seeing is the security model of classloaders ... classes in Solr can access classes in the container's classloader, but classes in the container's loader can't see classes in solr. Even if they are the same classes, they are differnet *instances* of those classes -- the Class obejcts themselves are distinct. If you're really concerned about minimizing duplication and having a really tiny footprint, reconstructing the solr war to contain all of your classes 9and removing anything you *don't* need) is your best bet ... but for 99% of the worl hat's going to be major overkill. -Hoss
