So that class is sitting naked in your .ear? Personally, I'd put it in a jar first, but that won't solve your problem.
> There has to be a better way. If I've got EJBs, JSPs
> and Servlets that all need access to the same utility
> classes, it seems that I'll have to include the same
> class in 3+ jar files (one or more ejb.jar files, the
> web.war, and the app.ear)? Has anybody got a good
> solution to this process problem? Having multiple
> copies of the same class file seems pretty dangerous
> to me.
Yep, blecherous. Why would you put it in your ear, though?
Try pre-compiling the JSP. When I've seen this problem it's been when the JSP is compiled - it should go away if you precompile the JSP so that it's just a servlet that gets run.