EAR vs RPM for web application delivery?

When sending a web application to production, do you consider the archive of the corporate application or RPM?

What are the pros and cons of each?

With RPM, you can keep track of versions and properly process configuration files.

Assume that your application will not be installed on windows, so OS dependency is not the issue we are worried about.

+5
source share
1 answer

Most of the Java web applications I've worked with or studied with are usually published as corporate or web archives. The case for RPM is rather weak, with the exception of very specific scenarios.

There are several points that favor EAR / WAR files:

  • , / EAR/WAR . . , Linux ( Java) , RPM. , , , ; , / .

  • EAR/WAR , . . , RPM ; RPM EAR/WAR . , , RPM EAR/WAR RPM, .

  • RPM , , WebLogic, WebSphere .. , , , , .. RPM, , , , .

EAR/WAR , RPM .

+4

All Articles