Darn I should of thought of that. We have similar class loader problems when using OSGi. Martin has provided an "escape" in the form of a FactoryIterator - but to my understanding you would need to provide your own implementation (probably based on whatever stuff Axis had going on).
Cheers, Jody Gertjan van Oosten wrote: > Hi Saul, > > As quoted from "Farber, Saul (EEA)" <[EMAIL PROTECTED]>: > >> I'm just back from vacation. Gertjan, do you have a full stack trace >> that you could send me? >> > > The full stack trace was attached to the first message in this thread. > I did solve it in the meantime by the way, but it wasn't easy to find. > The problem appeared in a web service that was running under the Axis2 > webapp inside an .aar (Axis service archive). When I tried to isolate > the problem in a stand-alone program, it went away. When I tried to > reproduce the problem in a webapp, it also went away. In the end it > turned out that Axis2 sets up its own classloader for .aar services, and > that classloader somehow failed to find the filter stuff. My solution > was simple after that: no longer use the Axis2 webapp with the .aar, > instead run my web services in their own webapp. > So now I have it working again you don't need to pursue this any > further, as far as I'm concerned. > > Kind regards, > ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
