Home | Site Map | News | Devzone | Downloads | Contact Us

Fiorano Developer Forum

  • July 24, 2017, 01:43:46 PM
  • Welcome, Guest
Advanced search  


Fiorano launches new MQ 10

Pages: [1]   Go Down

Author Topic: Fiorano Mapper: Do nested XSD's really need an absolute path?  (Read 4074 times)

Anton van Zanten

  • Newbie
  • *
  • Posts: 9

I'm using the Fiorano Mapper (Fiorano SOA 9.2.2) to do a transformation on a route.

When i try to load an XSD with nested XSD's as input, the only working solution seems to be to have the reference as an absolute path. Even in the case where the imported XSD's have been added to the "Schema Repository".

In the documentation i found:
"To load an imported XSD from this XSD file, you need to modify the XSD to include the absolute path of the imported and included XSDs. For example, if abc.xsd is stored at c:\hsbc\xsd then, modify the import statement in abc-include.xsd to specify schema location of abc.xsd as file:///C:/hsbc/xsd/abc.xsd, that is, <xs:import namespace="" schemaLocation="file:///C:/hsbc/xsd/abc.xsd"/>"

Shouldn't the Schema Repository facilitate working with relative paths when using nested XSD's? How can i use a nested XSD in the mapper with relative paths?


  • Full Member
  • ***
  • Posts: 156
Re: Fiorano Mapper: Do nested XSD's really need an absolute path?
« Reply #1 on: March 10, 2011, 06:25:29 AM »

Hi Anton,

If you add the referenced schema to repository there is no need to use absolute path.
You just have to point schemaLocation to the 'URI' that you specified while importing in repository.
so if URI is specified as abc.xsd then schemaLocation="abc.xsd" will work.

Pages: [1]   Go Up