1 Reply Latest reply on Aug 9, 2018 5:22 AM by ehugonnet

    Reloadable = false. Avoid reload server for simple xhtml code change.

    Daniel Gutiérrez Newbie
      Ha          dasdssddas

      Hello, everyone.

       

      I'm testing to start a JEE project.

       

      I've usually worked with Spring and Tomcat and Eclipse.

       

      In tomcat by default, if I modify a.xhtml the changes are reflected without restarting the server. They're instantaneous. If I enter the context.xml file and modify the reloadable="false" parameter, I can modify java and xhtml code in what we could call a hot deploy.

       

      However, with Wildfly by default, a simple change in a .xhtml makes an undeploy/deploy of the project, which becomes a nightmare. If I enter the options of RedHatDeveloperStudio -> Publishing -> Never publish automatically. The server never restarts and I can make changes to the java files, but it does not pick up the changes in the xhtml files.

       

      How hard is it to find a parameter similar to the reloadable="false"?

       

      I have worked with TomEE and it also has the option reloadable="false".

       

      Maybe Wildfly's not good at developing and better off leaving it for production?

        • 1. Re: Reloadable = false. Avoid reload server for simple xhtml code change.
          ehugonnet Apprentice

          Well it all depends on how you are working. Netbeans and Eclipse IDE's could do this for you using exploded deployments or writing an exploded archive in the deployments folder.

          I'm sure (since i wrote it) that replacing an HTML file will not fire a reload in both those cases.

          Now if you are producing an archive and deploying it then we don't know which file has changed and a reload will be required.

          There is no such things as a reloadable parameter.

          As for classes, reload is required (even if with 14 and fakereplace it will get better).