If you have downloaded the jboss-tomcat distribution, the default instance has the integrated tomcat already installed (jbossweb-tomcat.sar in the server/default/deploy directory). Running run.bat/run.sh without any arguments will start the default JBoss instance. Once started, you can drop your WARs into server/default/deploy directory and JBoss will automatically deploy your web application.
it looks like the problem is the classpath Ant (why is ant being used to compile jsp's?) is using is too long.
Here is why i think this:
I eliminated all my ejbs from the deploy folder and stuck in a non-related war which is known to work. I fired up JBoss and everything came up. I then accessed that war and it compiled the JSPs in it fine. So from this i gather Tomcat is configured correctly.
I stuck back in all my EJB's, without deploying the real war and left the other war in. Now, the jsp's in the war, which worked before i deployed my EJB's no longer work and i get the same error about:
12:12:59,745 ERROR [Engine] Exception:
Error running C:\java\j2sdk1.4.0_01\bin\javac.exe compiler
prior to this it lists a classpath about well...VERY...long. I have about 200 EJB's. The funny thing is it appears to list all the EJB's twice in the CLasspath.
I get no errors or warnings about any of my ejb's. These same ejbs deploy without error under JBoss 2.4.4. The same with my projects war.
Would deploying as an EAR help?