OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   Problem with relative paths when validating against xsd

[ Lists Home | Date Index | Thread Index ]
  • To: xml-dev@lists.xml.org
  • Subject: Problem with relative paths when validating against xsd
  • From: robert@elastica.com
  • Date: Tue, 30 Aug 2005 10:37:24 -0500
  • User-agent: Internet Messaging Program (IMP) 3.2.2

So I've got an application that runs inside Weblogic and validates xml against
xml schema thus.

String noNamespaceSchemaLocation = "PricingService/" + commandName +


Now this relative URI is relative to the CWD which is the Weblogic domain

What I don't understand is why this path is also necessary to validate relative
paths for all the .xsd files that lie in this directory.

So I have Common.xsd, Types.xsd that are under PricingService and are reused in
other .xsds that are also in PricingService but at runtime via <xsd:include
this paths are resolved relative to CWD and not relative to where they are
being included so I'm forced to specify <xs:include
schemaLocation="PricingService/Common.xsd"/> instead of just <xs:include
schemaLocation="Common.xsd"/> and this presents a problem in XMLSpy because
XMLSpy wants to resolve all paths relative to where they are included from not
from any notion of a CWD.

This message was sent using IMP, the Internet Messaging Program.


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS