Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
View | Details | Raw Unified | Return to bug 140042
Collapse All | Expand All

(-)topics/taddingfacet.html (-9 / +35 lines)
Lines 25-33 Link Here
25
you add a facet to a project, that project is configured to perform a certain
25
you add a facet to a project, that project is configured to perform a certain
26
task, fulfill certain requirements, or have certain characteristics. For example,
26
task, fulfill certain requirements, or have certain characteristics. For example,
27
the EAR facet sets up a project to function as an enterprise application by
27
the EAR facet sets up a project to function as an enterprise application by
28
adding a deployment descriptor and setting up the project's classpath.<p>New
28
adding a deployment descriptor and setting up the project's classpath.<p>You
29
projects generally have facets added to them when they are created. To add
29
can add facets only to J2EE projects and other types of projects that are
30
another facet to a project that already exists, follow these steps:</p>
30
based on J2EE projects, such as enterprise application projects, dynamic Web
31
projects, and EJB projects. You cannot add facets to a Java project or plug-in
32
project, for example. Typically, a facet-enabled project has at least one
33
facet when it is created, allowing you to add more facets if necessary. For
34
example, a new EJB project has the EJB Module facet. You can then add other
35
facets to this project like the EJBDoclet (XDoclet) facet.</p>
36
<p>Some facets
37
require other facets as prerequisites. Other facets cannot be in the same
38
project together. For example, you cannot add the Dynamic Web Module facet
39
to an EJB project because the EJB project already has the EJB Module facet.
40
Some facets can be removed from a project and others cannot.</p>
41
<p>New projects
42
generally have facets added to them when they are created. To add another
43
facet to a project that already exists, follow these steps:</p>
31
</div>
44
</div>
32
<ol><li class="stepexpand"><span>In the Project Explorer view, right-click the project and then
45
<ol><li class="stepexpand"><span>In the Project Explorer view, right-click the project and then
33
click <span class="uicontrol">Properties</span>.</span></li>
46
click <span class="uicontrol">Properties</span>.</span></li>
Lines 35-47 Link Here
35
<li class="stepexpand"><span>Click <span class="uicontrol">Add/Remove Project Facets</span>.</span></li>
48
<li class="stepexpand"><span>Click <span class="uicontrol">Add/Remove Project Facets</span>.</span></li>
36
<li class="stepexpand"><span>In the Add/Remove Project Facets window, select the check boxes
49
<li class="stepexpand"><span>In the Add/Remove Project Facets window, select the check boxes
37
next to the facets you want this project to have and select a version number
50
next to the facets you want this project to have and select a version number
38
for each facet.</span> You can also choose a preset combination of facets
51
for each facet.</span> <div class="p">Only the facets that are valid for the project
39
from the <span class="uicontrol">Presets</span> list, and you can find out more about
52
are listed:<ul><li>The list of runtimes selected for the project limits the facets shown
40
the requirements for each facet by right-clicking the facet name and then
53
in the list. Only the facets compatible with all selected target runtimes
41
clicking <span class="uicontrol">Show Constraints</span>.</li>
54
are shown.</li>
55
<li>The currently selected facets and their version numbers limit the other
56
facets shown in the list. For example, if the project contains the Dynamic
57
Web Module facet, the EJB Module facet is not listed because these two facets
58
cannot be in the same project.</li>
59
</ul>
60
You can find out more about the requirements and limitations for each
61
facet by right-clicking the facet name and then clicking <span class="uicontrol">Show Constraints</span>.</div>
62
<p>You
63
can also choose a preset combination of facets from the <span class="uicontrol">Presets</span> list.</p>
64
</li>
65
<li class="stepexpand"><span>To remove a facet, clear its check box.</span> Not all facets
66
can be removed.</li>
42
<li class="stepexpand"><span>If you want to limit the project so it will be compatible with
67
<li class="stepexpand"><span>If you want to limit the project so it will be compatible with
43
one or more runtimes, click the <span class="uicontrol">Show Runtimes</span> button
68
one or more runtimes, click the <span class="uicontrol">Show Runtimes</span> button
44
and select the runtimes that you want the project to be compatible with.</span></li>
69
and select the runtimes that you want the project to be compatible with.</span> For more information on runtimes, see <a href="tjtargetserver.html" title="When you develop J2EE applications, you can specify the server runtime environments for your J2EE projects. The target server is specified during project creation and import, and it can be changed in the project properties. The target server setting is the default mechanism for setting the class path for J2EE projects.">Specifying target servers for J2EE projects</a>.</li>
45
<li class="stepexpand"><span>Click <span class="uicontrol">Finish</span>.</span></li>
70
<li class="stepexpand"><span>Click <span class="uicontrol">Finish</span>.</span></li>
46
<li class="stepexpand"><span>Click <span class="uicontrol">OK</span>.</span></li>
71
<li class="stepexpand"><span>Click <span class="uicontrol">OK</span>.</span></li>
47
</ol>
72
</ol>
Lines 51-59 Link Here
51
<div class="parentlink"><strong>Parent topic:</strong> <a href="../topics/ph-projects.html" title="The workbench can work with many different types of projects. The following topics cover creating and managing some of the types of projects related to J2EE development.">Working with projects</a></div>
76
<div class="parentlink"><strong>Parent topic:</strong> <a href="../topics/ph-projects.html" title="The workbench can work with many different types of projects. The following topics cover creating and managing some of the types of projects related to J2EE development.">Working with projects</a></div>
52
</div>
77
</div>
53
<div class="reltasks"><strong>Related tasks</strong><br />
78
<div class="reltasks"><strong>Related tasks</strong><br />
54
<div><a href="../topics/tjear.html">Creating an enterprise application project</a></div>
79
<div><a href="../topics/tjear.html" title="">Creating an enterprise application project</a></div>
55
<div><a href="../topics/tjappproj.html" title="You can use a wizard to create a new application client project and add it to a new or existing enterprise application project.">Creating an application client project</a></div>
80
<div><a href="../topics/tjappproj.html" title="You can use a wizard to create a new application client project and add it to a new or existing enterprise application project.">Creating an application client project</a></div>
56
<div><a href="../topics/tjrar.html" title="A connector is a J2EE standard extension mechanism for containers to provide connectivity to enterprise information systems (EISs).">Creating a connector project</a></div>
81
<div><a href="../topics/tjrar.html" title="A connector is a J2EE standard extension mechanism for containers to provide connectivity to enterprise information systems (EISs).">Creating a connector project</a></div>
82
<div><a href="../topics/cjearproj.html" title="An enterprise application project ties together the resources that are required to deploy a J2EE enterprise application.">Enterprise application projects</a></div>
57
</div>
83
</div>
58
</div>
84
</div>
59
</body>
85
</body>
(-)topics/tjtargetserver.html (-19 / +19 lines)
Lines 25-31 Link Here
25
during project creation and import, and it can be changed in the project properties.
25
during project creation and import, and it can be changed in the project properties.
26
The target server setting is the default mechanism for setting the class path
26
The target server setting is the default mechanism for setting the class path
27
for J2EE projects.</div><div class="section"><p>In order to support different application servers that use different
27
for J2EE projects.</div><div class="section"><p>In order to support different application servers that use different
28
JDK levels for their Java™ Runtime Environment (JRE), the workbench
28
JDK levels for their Java™ Runtime Environment (JRE), the workbench
29
prompts you for a target server setting for each J2EE project. For example,
29
prompts you for a target server setting for each J2EE project. For example,
30
if you want to take advantage of the features of JDK 1.4.2, your applications
30
if you want to take advantage of the features of JDK 1.4.2, your applications
31
require different class path entries than those that were used in previous
31
require different class path entries than those that were used in previous
Lines 56-62 Link Here
56
for the resulting projects. The list of target servers that you can choose
56
for the resulting projects. The list of target servers that you can choose
57
from is filtered based on installed runtimes, the J2EE level of the application,
57
from is filtered based on installed runtimes, the J2EE level of the application,
58
and the J2EE module type. For example, for EJB projects only application servers
58
and the J2EE module type. For example, for EJB projects only application servers
59
that support Enterprise JavaBeans™ are displayed. All projects
59
that support Enterprise JavaBeans™ are displayed. All projects
60
inside a single EAR file must be targeted to the same server. If you create
60
inside a single EAR file must be targeted to the same server. If you create
61
a new project and add it to an existing EAR project during creation, the project
61
a new project and add it to an existing EAR project during creation, the project
62
inherits the target server setting of the EAR project.</p>
62
inherits the target server setting of the EAR project.</p>
Lines 70-93 Link Here
70
<ol><li class="stepexpand"><span>In the Project Explorer view of the J2EE perspective, right-click
70
<ol><li class="stepexpand"><span>In the Project Explorer view of the J2EE perspective, right-click
71
the enterprise application or module project, and select <span class="uicontrol">Properties</span> from
71
the enterprise application or module project, and select <span class="uicontrol">Properties</span> from
72
the pop-up menu.</span> The Properties dialog for the project opens.</li>
72
the pop-up menu.</span> The Properties dialog for the project opens.</li>
73
<li class="stepexpand"><span>Select the <span class="uicontrol">Project Facets</span> page on the Properties
73
<li class="stepexpand"><span>Select the <span class="uicontrol">Targeted Runtimes</span> page on the
74
dialog.</span></li>
74
Properties dialog.</span></li>
75
<li class="stepexpand"><span>Click the <span class="uicontrol">Add/Remove Project Facets</span> button.</span></li>
76
<li class="stepexpand"><span>In the Select Project Facets window, click the <span class="uicontrol">Show
77
Runtimes</span> button.</span> The <span class="uicontrol">Runtimes</span> list
78
shows all of the runtimes in your workspace. The grayed-out runtimes are not
79
compatible with the currently selected project facets. The runtime in bold,
80
if there is one, is the preferred runtime for the project.</li>
81
<li class="stepexpand"><span>In the <span class="uicontrol">Runtimes</span> list, select the check boxes
75
<li class="stepexpand"><span>In the <span class="uicontrol">Runtimes</span> list, select the check boxes
82
next to the runtimes you want to develop the project for.</span> The runtimes
76
next to each of the runtimes that you want to develop the project for.</span> <p>Only the runtimes compatible with the project's facets are shown.
83
you select filter the list of available facets in the <span class="uicontrol">Project Facet</span> list.<p>If
77
You can select the <span class="uicontrol">Show all runtimes</span> check box to display
84
you select any runtimes for the project, you must make one of those runtimes
78
the runtimes not compatible with the project's current facet configuration.
85
the preferred runtime for the project. If you select only one runtime from
79
These runtimes are grayed out.</p>
86
the list, that runtime is automatically made the preferred runtime.</p>
80
<p>If you don't see the runtime that you
81
want to use, you need to add it to the runtimes in the workbench. See <a href="../org.eclipse.wst.server.ui.doc.user/topics/twinstprf.html">Defining the installed server runtime environments</a>.</p>
82
</li>
83
<li class="stepexpand"><span>To select the primary runtime, click on a runtime and then click
84
the <span class="uicontrol">Make Primary</span> button.</span> <p>If you select
85
any runtimes for the project, you must make one of those runtimes the primary
86
runtime for the project. If you select only one runtime from the list, that
87
runtime is automatically made the primary runtime. The primary runtime is
88
shown in bold text.</p>
87
</li>
89
</li>
88
<li class="stepexpand"><span>To select the preferred runtime, click on a runtime and then click
89
the <span class="uicontrol">Make Preferred</span> button.</span> The preferred
90
runtime is shown in bold text.</li>
91
<li class="stepexpand"><span>Click <span class="uicontrol">Finish</span>.</span></li>
90
<li class="stepexpand"><span>Click <span class="uicontrol">Finish</span>.</span></li>
92
<li class="stepexpand"><span>Click <span class="uicontrol">OK</span>.</span></li>
91
<li class="stepexpand"><span>Click <span class="uicontrol">OK</span>.</span></li>
93
</ol>
92
</ol>
Lines 99-103 Link Here
99
<div class="relconcepts"><strong>Related concepts</strong><br />
98
<div class="relconcepts"><strong>Related concepts</strong><br />
100
<div><a href="../topics/cjarch.html" title="The Java 2 Platform, Enterprise Edition (J2EE) provides a standard for developing multitier, enterprise services.">J2EE architecture</a></div>
99
<div><a href="../topics/cjarch.html" title="The Java 2 Platform, Enterprise Edition (J2EE) provides a standard for developing multitier, enterprise services.">J2EE architecture</a></div>
101
</div>
100
</div>
102
</div></body>
101
<div><strong>Related information</strong><div><a href="../../org.eclipse.wst.server.ui.doc.user/topics/twinstprf.html">Defining the installed server runtime environments</a></div>
102
</div></div></body>
103
</html>
103
</html>

Return to bug 140042