Details

    • Epic/Theme:
    • Liferay Contributor's Agreement:
      Accept
    • Similar Issues:
      Show 5 results 

      Description

      Enables Ext Plugin to hot redeploy the way as other plugins do.

      See: http://www.liferay.com/community/forums/-/message_boards/message/6700511

      Implemented solution:

      Automatic solution 1:

      • ignore standard undeploy event, just flag that there was such attempt
      • in deploy phase check for undeploy flag (which cannot persist container reboot) and if so then do redeploy

      Differences from how it works now:
      1, when you deploy your Ext Plugin, ExtHotDeployListener backup replaced JSPs, web.xml and other replaced files
      2, when you copy your Ext Plugin war file into deploy directory then
      2a, container stops application -> ExtHotDeployListener place the application's name into list of possible-to-redeploy applications (this is the "flag")
      2b, container installs new application and invoke application start -> ExtHotDeployListener check if the application is among the possible-to-redeploy applications and if so then:
      2b I, remove Ext Plugin's registered jars
      2b II, restore web.xml backup
      2b III, restore backups of other replaced files (JSPs, struts-config-ext.xml, etc.)
      2b IV, delete WEB-INF/ext-"servletContextName".xml
      2b IV, unregister Ext Plugin from ExtRegistry (for conflict checking)
      2c, continue as normal -> install new version of Ext Plugin

        Activity

          People

          • Votes:
            15 Vote for this issue
            Watchers:
            11 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development

                Structure Helper Panel