Yep this fixed it. Brian Frutchey Federal Solutions Architect M (703) 597-4875 E [email protected] Endeca 2100 Reston Parkway Ste 101 Reston, VA 20171 www.endeca.com find / analyze / understand
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Mck Sent: Friday, August 28, 2009 1:01 PM To: [email protected] Subject: RE: classloader issue > Actually, it looks like the federatorRunHandler is what is getting the > different classloader as neither of my search commands share it. Yeah sorry was a bit confused there. Looking through Spi what i see start up is from the classloader responsible for FederatorRunHandler, that is Spi.RUN_HANDLER_CONTROL, has no way to load anything from the Spi.RESULT classloaders. (Because the Spi.RUN_HANDLER_CONTROL has the parent Spi.RUN_HANDLER_CONFIG and it stops there.) It might help if Spi.RUN_HANDLER_CONFIG has the parent Spi.RESULT In Spi try replacing the line RUN_HANDLER_CONFIG("run-handler-config"), with RUN_HANDLER_CONFIG("run-handler-config", RESULT), and rebuild sesat-kernel and run. ~mck -- "This above all: to thine own self be true. It must follow that you cannot then be false to any man." Shakespeare | semb.wever.org | sesat.no | finn.no | _______________________________________________ Kernel-development mailing list [email protected] http://sesat.no/mailman/listinfo/kernel-development
