I noticed this same behavior when I accidentally had the package statement wrong and the class file inside the JAR was put in the wrong directory (since fixed).
Could the same behavior be exhibited when there is something wrong with the class itself? How can I debug this?
Thanks!