pombreda / fits

Automatically exported from code.google.com/p/fits
GNU Lesser General Public License v3.0
0 stars 0 forks source link

using relative path instead of $FITS_HOME/path in xml/nlnz/config.xml & in XSLT when for xml/fits_output.xsd #3

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

1) XSLT is used to convert each tools output into the FITS XML format. When
it does this it's using the relative path "xml/fits_output.xsd" as the
schema location, without the FITS_HOME variable.  From a current directory
other then FITS_HOME, the schema cannot be found, so the FITS XML output
cannot be validated and the 'invalid fits xml output' messages are displayed.
--> workaround = disable validate-tool-output in xml/fits.xml

2) A similar thing is happening to NLNZ.  In xml/nlnz/config.xml the
<xml-location> is set to "xml/nlnz"- another relative path.  
--> workaround = set this to $CURDIR/xml/nlnz (i.e. absolute path)

Cheers
David Michel

Original issue reported on code.google.com by dmiche...@googlemail.com on 26 Aug 2009 at 10:19

GoogleCodeExporter commented 9 years ago
The workaround I found was to set user.dir to the FITS home absolute path:
System.setProperty("user.dir", new File(Fits.FITS_HOME).getAbsolutePath());
This isn't currently an issue however it could become an annoying constraint.

Original comment by Seth.E.S...@gmail.com on 2 Nov 2009 at 4:42

GoogleCodeExporter commented 9 years ago
yes, I guess that would work. However, changing user.dir is, as you said, an 
annoying
constraint as I'm already using user.dir for others things...

Original comment by dmiche...@googlemail.com on 2 Nov 2009 at 5:00

GoogleCodeExporter commented 9 years ago

Original comment by spencer_...@harvard.edu on 14 Jan 2010 at 7:31