Options:
1) Set them up as a Java project. Then use the "make zip" plugin to have the compiled classes moved into a jar file in the EAR whenever the project is rebuilt. (You can put a Java project on the build path of your web project, but this does not address the need for the classes to be on the runtime classpath for the server. Making a jar and adding it to the EAR does this.) (ALSO - you'll need to reference the jar from the manifest file of your WAR - the "add module dependencies" wizard does this for you.)
2) Jar them and put them in the lib folder of your WAR. You can associate a "source jar" with the jar in WSAD so that you can debug. (Don't remember the exact steps - would need to look it up.)
Which is better? Depends. If the classes will be used by other projects, including any new web projects or an
ejb project, use #1. If the classes are simply support files for the single web project, use #2.
Matt
p.s. If I hadn't just passed 157 I probably wouldn't be remembering any of this (grin).
[ May 21, 2002: Message edited by: Matthew Comer ]