Put the jar to be downloaded relative to the pages of your app, don't hide it under WEB-INF
I found the problem.
For some reason all I needed to do was provide the full path name
of the class. IE com.packagename.classname.
There must be a bug in jboss as the imports did not do their job
Encoding classes with their fully qualified names is a java 101 issue that has nothing to do with jboss.