Use JDK 1.4 and run JBoss in debug mode so that when you make a change in Eclipse and recompile (save the file) it will be updated on-the-fly without any redeployment whatsoever. Also, do not use an EAR for development but rather loose jar files and an exploded war file. Then you can granulate Ant tasks to update specific jars. You have to touch web.xml to redploy a war, analogous to touching application.xml to redeploy an ear.
Thanks! I will try it.
By loose jar files do you mean that I put my .jar files directly in /deploy folder of jboss??
I also use a lot of hot code replace of jbosside, but some times it isn't possible.
I'm using jdk1.4.2_03
Having said all that, the number one strategy to speed development in JBoss or anything else is a testing framework that allows you to exercise components individually. You can use Cactus to test server-side components and I highly recommend doing so.
Ok. I will try this too.
Thanks for your feedback Rod.
-- Regards,
Francisco Figueiredo Jr. Membro Fundador do Projeto MonoBrasil - MonoBrasil Project Founding Member
------------- "Science without religion is lame; religion without science is blind."
~ Albert Einstein
------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
