> It appears to be finding it; if I change the schema value to something that > doesn't exist, it generates an error at startup: Ok. Then my guess is your XML that's invalid isn't in fact invalid, in some subtle way. -- Scott