Multiple saxon jars in libext will cause process-files.ktr to fail

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Have saxon9.jar and saxon9-dom.jar in libext folder.

What is the expected output? What do you see instead?
process-files.ktr should run without issue.

What version of the product are you using? On what operating system?
Kettle-trunk rev 14743 Ubuntu/Win7

Please provide any additional information below.
The "Get Saxon Jar" step in process-files should have an exclude regex applied 
so only 1 file matches. Multiple file matches is what causes the issue.

I added .*dom.* to the "exclude wildcard" column, which fixes the problem if 
you have saxon9-dom.jar in your libext folder.

Original issue reported on code.google.com by mane...@amerch.com on 10 Feb 2011 at 4:31

[GoogleCodeExporter]

Hi! 

thanks for reporting this. Actually I would assume you'd run into trouble 
running kettle if you have multiple saxon jars, is that not the case? 

Also, I think I tried with saxon9 (as opposed to the saxon8 that ships with 
kettle) and I seem to recall that not working since it accepts different 
arguments on the command line, is that correct? Or is it working for you?

thanks in advance, and kind regards,

Roland

Original comment by roland.bouman on 10 Feb 2011 at 4:43

• Changed state: NeedFeedback

[GoogleCodeExporter]

It works fine now. It's not that I have multiple saxon jars, but multiple
different jars that start with the letters saxon. They are saxon9.jar(4.8mb)
and saxon9-dom.jar(126k)

The error was multiple files matching and being passed through. The set
values step expects 1 row.

I'm building from trunk and have not added/modified/removed any jars from
the libext folder, so I would think they have moved to saxon9 and included
the saxon9-dom jar as well.

BTW, Thanks for the amazing documentation tool!

Brandon.

Original comment by mane...@amerch.com on 10 Feb 2011 at 5:06

[GoogleCodeExporter]

Brandon, 

thanks for your clarification, and sorry for misunderstanding you. Yes I agree, 
I should modify the regex to exclude at least all known saxon libs that might 
be in there that are not the xslt processor.

(thanks for using kettle-cookbook and contributing issue reports - it is much 
appreciated :)

Original comment by roland.bouman on 10 Feb 2011 at 5:29

• Changed state: Accepted

[GoogleCodeExporter]

Unfortunately I cannot use the proposed fix since kettle 3.2 does not support a 
"exclude wildcard" feature. 

The fix is in r71 and consists of making a top-level parameter of the saxon 
location, with a default of ./libext/saxon8.jar. This should also fix issue 36

Original comment by roland.bouman on 3 Apr 2011 at 9:39

• Changed state: Fixed