You should look at putting the jar file on the client's machine as any macro runs on the client and not on the server... Just a thought, have not done something like this myself... :)
Thanks for the suggestion, Francois. I tried putting the jar file on the client machine and set the PATH. Running the macro gives the same error.
I thought that importing in the macro itself would make the jar file available at runtime?