>Your cron apparently is accessing a different JVM than the command line
process
>Make sure that cron calls a java VM that is recent enough to run saxon

I had this kind of thing happen to me several times. The cron job does not
have the same environment that you have. (when you login in your .bashrc and
profile set up your environment). What I've found is that complete paths are
needed to all directories and executibles.

--Brian