Java Web Application - Deployment Strategy Alternative to WAR - Manage user interface changes separately from patches with a full code base

I heavily edited this question because the answers showed that I was not clear

problem: user interface changes in a Java web project can be tedious and time consuming because every web application file is contained in a WAR

my suggested solution: Manage JSP, CSS, JS and tags separately from the application code base, which I define for this question as:

  • All Java source code
  • Compiled Java Custom Tag Libraries (TagSupport Extension)
  • Spring Configuration Files
  • web.xml
  • Jar's
+ Source
+ WEB
   - WEB-INF
      - JSP
      - Tags
      - lib
   - HTML
   - CSS
   - JS

, , . , . , CSS/JS/HTML JSP , , .. JSP , ( ) JSP , - .

CASE. , HTML- , ​​ .

: UI dev Dreamweaver FTP Staging ( , ). :

   - JSP
   - Tags
   - HTML
   - CSS
   - JS

HTML , HTML. JSP/home.jsp , , , , URL. , . , ,

$ staging - > ./rollbackView -mostRecentBackup

UI , , . HTML, , JSP. QA, , , , . .

$ production - > ./updateProductionView

script , , . 8:45 - ( ) , 15 .

, - , . , , script , Mercurial, (?), , . , . , , WAR Staging

$ staging - > ./deployStaging -overwriteView

, JSP , . UI , (, ?). "-overwriteView", . , QA,

$ staging - > ./deployProduction

, V1.1,

:

-, - - ? , , ? Windows, Unix. Tomcat.

, Staging , , , ,

? ? CVS?

-, ?

+3

Source: https://habr.com/ru/post/1752367/


All Articles