New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Better handling of missing saxon jar #62

Open

GoogleCodeExporter opened this issue Aug 13, 2015 · 2 comments

Labels

auto-migrated Priority-Medium Type-Defect

GoogleCodeExporter commented Aug 13, 2015

I suggest that in "create-transform-script.ktr" you have a "detect empty 
stream" on the saxon jar and ABORT the process if it isnt found.

See attached as an example!
(Failing to find the saxon jar does seem to be a bit of an ongoing historic 
issue. Problem in PDI 5 is that it's now called saxon-9.<lots of version 
numbers>.jar!

Original issue reported on code.google.com by d.e.kee...@gmail.com on 18 Dec 2013 at 9:47

Attachments:

create-transform-script.ktr

The text was updated successfully, but these errors were encountered:

GoogleCodeExporter added Priority-Medium Type-Defect auto-migrated labels

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment