I answered my own question, in case this helps someone else.
STAX goes and asks for the current thread's default class loader. I hadn't set that to the loader in which I was operating. ________________________________ From: Benson Margulies [mailto:[EMAIL PROTECTED] Sent: Monday, December 25, 2006 12:45 PM To: [email protected] Subject: [xfire-user] A class loader pickle of some sort with STAX I have everything operating normally when running in the standard classloader. For various reasons, I have concocted a 'stick all the jars in this directory onto the classpath' classloader. Running inside that, the STAX API jar goes looking for the BEA reference implementation instead of for the woodstox version. If anyone out there happens to have an idea, off hand, of what would cause this, I'd be grateful.
