Minor code change causes complete WAR redeploy, how to fix i

[sbarkdull]

I am developing a jsp/servlet app using Eclipse 3.4.2 with the Web Tools Platform (JBoss Tools) and jboss 4.2.3.

I have configured the JBoss server, in Eclipse, to "Never publish Automatically".

After I have JBoss started from Eclipse's "Server View", if I change a file (a .jsp, .html, .js or .java), and tell Eclipse to publish the changes by right clicking on the server in the server view and selecting "publish", Eclipse (or JBoss Tools?) rebuilds the entire war, copies it down to JBoss's "server/default/deploy" directory, and then explodes the WAR.

It seems it would be faster to simply copy the changed files down to the exploded WAR. I believe that this is exactly what Tomcat does when running inside of Eclipse / WTP, and file chages are lightening fast. Even with moderately sized apps, JBoss/Eclipse/JBoss Tools takes over a minute to redeploy a trivial change to an html file.

Can anyone explain how to get JBoss to publish changes FAST like Tomcat/WTP?

[maxandersen]

If you have configured eclipse to Never publish automatically then neither Jboss nor tomcat in WTP will be fast :)

We copy changes incrementally to the exploded location by default so not sure why you are saying we are rebuilding the entire war (that should only happen if you are doing a full publish).

Are you actually using *our* server adapter and not the WTP one ?

The JBoss WTP one will rebuild the entire war, we don't.

[sbarkdull]

Thank you for your response Max.

I switched to the JBoss server adapter (instead of the WTP server adapter), configured it to "automatically publish when resources change", and now it deploys incrementally, is fast and behaves as I'd hoped.

[maxandersen]

Good - you got me scared there for a second ;)