packages\YOURPACKAGE\code\jars is correct. The lib directory is for JNI stuff as far as I know (never had a need to use it).
You need to reload the package for the classloader to pick it up. As is the case if you want to use a new version. Perhaps that’s the only reason?
Other possibilities:
- permissions on the file… can the Integration Server’s kick off user read it (in case you ftp’d it in with a different user or something)
- naming: it is called something.jar?
- corruption: the jar is ok (again: if FTP-ing it in, might have been in ascii mode or something)
- typos, check your java code, due to the dodgy text fields only editor it might just be a case of a typo stuffing things up.
regards,
Nathan Lee
#Integration-Server-and-ESB#Flow-and-Java-services#webMethods