blob: 006769a474966cf0358fb6ff86314bebf4f68217 [file] [log] [blame]
kprice9c922d82006-08-30 22:07:19 +00001<?xml version="1.0" encoding="utf-8"?>
2<!--Arbortext, Inc., 1988-2006, v.4002-->
3<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
4 "concept.dtd">
5<concept id="ccwebvw" xml:lang="en-us">
6<title>Project Explorer view and Web development</title>
7<prolog><metadata>
8<keywords><indexterm>Project Explorer view<indexterm>overview</indexterm></indexterm>
9<indexterm>Web perspective<indexterm>project explorer view</indexterm></indexterm>
10<indexterm>version control management<indexterm>turning on and off</indexterm></indexterm>
11<indexterm>Web development<indexterm>Project Explorer view</indexterm></indexterm>
12<indexterm>version control management<indexterm>turning on and off</indexterm></indexterm>
13</keywords>
14</metadata></prolog>
15<conbody>
16<section><p>The Project Explorer view provides the following notable features: <ul>
17<li><image alt="For Windows" href="../images/nwin.gif" placement="inline">
18</image> You can drag and drop files from <tm tmclass="special" tmowner="Microsoft Corporation"
19tmtype="reg" trademark="Windows">Windows</tm> Explorer or the desktop into
20the Navigator view.</li>
21<li>View filtering is supported by selecting <ph><uicontrol>Filters</uicontrol></ph> from
22the Navigator view <ph><uicontrol>Menu</uicontrol></ph> button. Resources
23can be filtered by name, project type or content type. Files beginning with
24a period are filtered out by default.</li>
25<li>The status line shows the full path of the selected resource.</li>
26<li>Dragging a .java file from the Navigator view into a JSP file will insert
27a usebean tag, the same behavior that is exhibited when a .class file is dragged
28into a JSP file.</li>
29<li>Errors and warnings on resources (including <tm tmclass="special" tmowner="Sun Microsystems, Inc."
30tmtype="tm" trademark="Java">Java</tm>, HTML/JSP, and Links Builder errors
31and warnings) are indicated with a red error <image alt="Error icon" href="../images/nshowerr.gif"
32placement="inline"></image> or yellow warning <image alt="Warning icon" href="../images/nwarning.gif"
33placement="inline"></image> next to the resource with the error, as well as
34the parent containers up to the project. This applies for all project types,
35not only Web projects.</li>
36<li>Items available from the <ph><uicontrol>New</uicontrol></ph> cascading
37menu in the project pop-up menu are context sensitive. All menus will have <ph><uicontrol>Project</uicontrol></ph> and <ph><uicontrol>Other</uicontrol
38></ph> options.</li>
39</ul></p></section>
40<section><title>Organization of the Project Explorer view</title><p>The Project
41Explorer view shows a custom view of all Web projects. The following are some
42of the notable top-level objects that appear beneath the project node (based
43on default folder names).</p><p><b>Web content folder</b> - This folder contains
44items to be published to the server. By default, this folder will be named <b>WebContent</b> for
45newly created static and dynamic Web projects. <note>You can change the name
46in the creation wizard Web facet page.</note><ul>
47<li><b>META-INF</b> - This directory contains the <filepath>MANIFEST.MF</filepath> file,
48which is used to map class paths for dependent JAR files that exist in other
49projects in the same Enterprise Application project. An entry in this file
50will update the run-time project class path and <tm tmclass="special" tmowner="Sun Microsystems, Inc."
51tmtype="tm" trademark="Java">Java</tm> build settings to include the referenced
52JAR files.</li>
53</ul><ul>
54<li><b>WEB-INF</b> - The directory where supporting Web resources for a Web
55application are kept (for example: .xmi files, .xml files, and web.xml.) </li>
56</ul> </p> </section>
57</conbody>
58</concept>