We've run in to this before as well. Is there any reason you can't just change the schema locations to point to local files? That was the only truly reliable method we could find that worked across all our XML processing stacks.
On Mon, Oct 17, 2011 at 08:16, Mark R Maxey <mark_r_ma...@raytheon.com> wrote: > > Thank you again for your insight and thorough response. This rocks our world, > but seeing the light is better than living in darkness. > > As I mention before, our problem is that we have hundreds of XSDs with > un-resolvable schemaLocations. We use JAXB to generate the XML-to-Java > binding and JAXP to do XSD validation. Since JAXB equated the namespace to > the publicId, we mistakenly thought JAXP would as well. > > My take away from all of this is that the only reliable, standards based, > cross parser solution to our problem is to generate an XML catalog containing > systemId mappings for each XSD. If anyone else has another solution, I'd be > interested in hearing it. -- Chad La Joie www.itumi.biz trusted identities, delivered --------------------------------------------------------------------- To unsubscribe, e-mail: j-users-unsubscr...@xerces.apache.org For additional commands, e-mail: j-users-h...@xerces.apache.org
