I guess what I'd rather have for the second part of the schemaLocation is a plain xsd filename and the XML stuff use some kind of path mechanism to find the file, but I'll try out an XMLEntityResolver and see how that goes. Thanks for the help again Dave.
On Thu, Jan 7, 2010 at 1:51 PM, David Bertoni <[email protected]> wrote: > On 1/7/2010 8:21 AM, Kelly Beard wrote: >> >> Ugh. I am so dumb. Nevermind. Before I had this: >> >> <?xml version="1.0" encoding="UTF-8" standalone="no" ?> >> <authNotify >> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; >> xmlns="http://www.quikq.com/xsd/authNotify"; >> xsi:schemaLocation="http://www.quikq.com/xsd/authNotify >> authNotify.xsd"> >> >> I changed it to this: >> >> <?xml version="1.0" encoding="UTF-8" standalone="no" ?> >> <authNotify >> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; >> xmlns="http://www.quikq.com/xsd/authNotify"; >> xsi:schemaLocation="http://www.quikq.com/xsd/authNotify >> /home/dfcuser/authNotify.xsd"> >> >> Initially it didn't work this way either. I scratched my head >> thinking that I knew I had XSD's in my HOME directory, what could be >> wrong? Well, my home directory isn't /home/dfcuser and I had no XSDs >> there at all. I copied them over and all is good now. If you specify >> no path the parser defaults to the same directory as the instance >> document. At least I have this email to remind me when dumbness >> strikes again. :-) > > You can also use an EntityResolver to accomplish this without modifying your > schema documents. Search the archives for more information, or take a look > at the Redirect sample application. > > Dave > -- Kelly Beard
