Can't get command line version to work

I've successfully downloaded, installed and used the Pipeline GUI. However I can't get the command line version to work. I downloaded and installed the command line version from the pipeline-20100125.zip file and updated the pipeline.user.properties. I'm using Windows Vista 64-bit. I've tried a number of scripts and they all fail. The app does seem to start o.k. since if I don't give the correct number of parameters it tells me and fails gracefully. Otherwise I get this stack trace. I've tried a number of different scripts with the same behavior so I assume there is something wrong with the enviroment. ... STATE] Task DTBook to XHTML just started [DEBUG, ???] Job Parameters: - input:pipetest.xml - output:xyz - daisyNoterefs:false - genToc:false - genChunks:false - charsetSwitcherEncoding:utf-8 - charsetSwitcherLineBreaks:default - validatorOutputXMLReport: [STATE] Transformer DTBook to XHTML just started [ERROR, Pipeline Core] Unexpected Error. org.daisy.pipeline.exception.JobFailedException: Error running script: Unexpected Error.. at org.daisy.pipeline.core.script.Runner.execute(Runner.java:124) at org.daisy.pipeline.core.PipelineCore.execute(PipelineCore.java:280) at org.daisy.pipeline.ui.CommandLineUI.main(CommandLineUI.java:213) java.lang.NullPointerException at uk_rnib_dtbook2xhtml.DTBook2Xhtml.execute(DTBook2Xhtml.java:122) at org.daisy.pipeline.core.transformer.Transformer.executeWrapper(Transformer.java:174) at org.daisy.pipeline.core.transformer.TransformerHandler.run(TransformerHandler.java:124) at org.daisy.pipeline.core.script.Runner.execute(Runner.java:98) at org.daisy.pipeline.core.PipelineCore.execute(PipelineCore.java:280) at org.daisy.pipeline.ui.CommandLineUI.main(CommandLineUI.java:213)

Can you please give me the

Can you please give me the full command line you tried to execute (with parameters) ? Given the line number of the exception it seems to be related to code that tries to get the path of the input/output file's directories... Thanks, Romain.

Ok, it works if I use full

Ok, it works if I use full pathnames for the input and output files. I was mislead since apparently the validator only requires the name of the file when it is in the directory I'm running from. Thank you so much, Susan P. S. Having spent many years as a developer supporting users it's a bit strange to be one of those annoying code (ab)users myself!

Oh, don't be sorry... if the

Oh, don't be sorry... if the failure message is not explicit about the cause it is certainly the fault of the developers and not the end user :) I will try and see if I can improve the path handling or at least the reporting in the next version. Thanks, Romain.

same issue

i got same issue.. i will follow the thread thank you.. Hollywood Graphic Design

Copyright © 2012 The DAISY Consortium, Some Rights Reserved.
Creative Commons License: No Derivative Works
Creative Commons

Valid XHTML 1.0!