Differences between the ear and war package structures

Structures and differences of ear, war, and jar files

Q: What are the differences between the new applications deployed in weblogic8. the application EJB module and the web application module connector module?

 

If an application contains EJB, JSP, and Servlet, the deployment steps are as follows:
(1) generate the ejb jar file. The best JAR file corresponds to an EJB
(2) generate a war file for the web application, register it in Web. xml and weblogic. XML, and configure Servlet and JSP.
(3) create an application. xml file and set the attributes of the application. Package application. XML, *. jar, *. war into a *. Ear file.
(4) register the application on the Weblogic console or copy the ear file to the application directory.

 

The structure of these files is listed below

Ear file structure

(Ear files in the sun-application.xml is the vendor-specific files, such as weblogic. XML, JBoss. XML can be)

For example, the structure of a typical ear file is:

MyApp. Ear

Myejb1.jar

Myejb2.jar

Myweb. War

META-INF/application. xml

Myres.rar

 

 

 

EJB file structure

(Sun-ejb-jar.xml is also specific, with the server type and change)

 

Web module File structure

(Sun-web.xml is also specific, with the server type and change)

 

Other problems:

Again: mydomain/applications/app1 myserver \. wlnotdelete \ extract \ myserver_app1 is the cache of the former?

 

Yes, WebLogic only accesses the compiled content in the production mode. WLS will automatically update the compiled file only when the parameters are set.

Differences between the ear and war package structures