1Z0-599 · Question #13
A web application is bound to the context named "/webapp" and the client uses the browser and Where do you place this resource inside the web application structure?
The correct answer is A. in the subdirectory /WEBINF/ctxl. The WEBINF directory contains the deployment descriptors for the Web application (web.xml and weblogic.xml) and two subdirectories for storing compiled Java classes and library JAR files. These subdirectories are respectively named classes and lib. JSP taglibs are stored in the…
Question
A web application is bound to the context named "/webapp" and the client uses the browser and Where do you place this resource inside the web application structure?
Options
- Ain the subdirectory /WEBINF/ctxl
- Bin the subdirectory /METAINF/ctxl
- Cin the subdirectory /ctxl in the root of the archive
- Din the subdirectory /ctxl/resource in the root of the archive
- Ein the root of the archive
How the community answered
(28 responses)- A93% (26)
- B4% (1)
- E4% (1)
Explanation
The WEBINF directory contains the deployment descriptors for the Web application (web.xml and weblogic.xml) and two subdirectories for storing compiled Java classes and library JAR files. These subdirectories are respectively named classes and lib. JSP taglibs are stored in the WEBINF directory at the top level of the staging directory. The Java classes include servlets, helper classes and, if desired, precompiled JSPs. Web applications use a standard directory structure defined in the Java EE specification. You can deploy a Web application as a collection of files that use this directory structure, known as exploded directory format, or as an archived file called a WAR file. Oracle recommends that you package and deploy your exploded Web application as part of an enterprise application. This is an Oracle best practice which allows for easier application migration, additions, and changes. Also, packaging your Web application as part of an enterprise application allows you to take advantage of the split development directory structure, which provides a number of benefits over the traditional single directory structure. Not B: METAINF is used by enterprise applications descriptors.
Topics
Community Discussion
No community discussion yet for this question.