[puppetmasta]

When I use MyEclipse to deploy and then start an application to JBoss (4.0.5 GA) I am getting the following error upon startup :

09:07:58,163 ERROR [MainDeployer] Could not create deployment: file:/D:/jboss-4.0.5.GA/server/myserver/deploy/myapp.war/
java.lang.NoClassDefFoundError: javax/servlet/http/HttpServlet

When I start JBoss manually, everything loads just fine. I think the issue is that MyEclipse is somehow setting the classpath incorrectly when starting JBoss.

To further prove this theory, I used an older workspace (that was setup before upgrading to MyEclipse 5.x.x). The application I have deployed to JBoss within this workspace loads just fine within JBoss. So what I did to test this, was to deploy the app that isn’t loading right to the same server as the app that is loading right. So I have 2 apps deployed to the same server. When I start JBoss from the old workspace, both apps load correctly!! If I start the JBoss server from the new workspace, both apps fail with java.lang.NoClassDefFoundError: javax/servlet/http/HttpServlet error.

This leads me to believe that somehow my old workspace is starting JBoss with a different set of parameters than the new workspace.

Is this a bug? A known issue? I have the most recent version of Eclipse (3.2.2) and MyEclipse 5.1.1.

Thanks,
Dave

[Riyad Kalla]

Dave,
In your new workspace, head on over to Window > Prefs > MyEclipse > App Servers > JBoss 4 > Paths, and make sure all the boxes are empty. MyEclipse by default will pickup all the server libs. If you need to augment the default classpath in any way, that is what you can use that screen for.

Also, I would go into your D:/jboss-4.0.5.GA/server/myserver/deploy/myapp.war/ directory, under the WEB-INF/lib dir, and make sure that your J2EE libraries aren’t accidentally getting deployed with your app since they already exist in the app server install (e.g. servlet API JARs, JSP, j2ee.jar, etc.)

[Author]

Posts