1 Reply Latest reply on Nov 2, 2007 3:38 AM by BeArt@QNH

    Prevent automatic deployment of whole application on mxml file changes

      I am using the Eclipse Builder 3 Beta 2 plugin for Eclipse 3.3 and have several java projects (hibernate + service layer) and one WTP Flex Project. I use Tomcat 6.0 as the application server.

      Tomcat started from eclipse and deployes the flex war. the Spring beans are loaded in the web.xml using hte contextloader.

      I encounter lots of Java Heap Space errors when changing small properties in the mxml files because it deploys the whole java applications on the server, but these are not changed at all.

      Sometimes only changes are compiled in the background and everything works as expected, but I am unable to reproduce this!! What kan I do that only changed MXML and Actionscritp files are published to tomcat without reloading the whole application?