jbx-j2eebuild.html

java bian xie de cheng xu, henhao de a

<br>
To select file types to be copied over to the project's output path and
the module directory :<br>
- Project|Project Properties. Click the Build|Resource page and
select the custom file type and select the Copy option. You
will have to refresh and make the project after this step before
rebuilding the module.<br>
<span style="font-style: italic;">This will automatically add an
include filter for the file type to EJB modules. You will have to add
an include filter for this file type for all other modules
(**/*.&lt;file type&gt; in the Content|Classes property page for the
module).</span><br>
<span style="font-weight: bold; font-style: italic;"><span
 style="font-style: italic;"></span></span>
<h2>Example Build Scenarios<br>
</h2>
<!--BNDX="iPlanet 6.0:startup process"--><!--BNDX="startup process:iPlanet 6.0"-->
<p><span style="font-weight: bold;">EJB JAR without any bean classes
(only stubs/skeletons and descriptors)</span><br>
Note : This example uses WebLogic<br>
- Right click the EJB module and choose Properties.<br>
- Click the Build|WebLogic page and uncheck the Remove Project Output
Path from Classpath option<br>
- Click the Content|Classes page, click the Add Filter page,
click the Exclude button and add the following filter: &lt;package
name&gt;/**<br>
</p>
<p><span style="font-weight: bold;">EJB JAR with custom files<br>
</span>Note : This example adds .dat files to the EJB JAR. Please
ensure that you create a .dat file in the project's source path for
this test.<br>
- Tools|Preferences. Click the Browser|File Types page. Select Generic
Resource File in the Recognized File Types list box.<br>
- Click the Add button. Enter dat and click OK<br>
- Project|Project Properties. Click the Build|Resource page. Select
dat and click the Copy button.<br>
- Right click the EJB Module and select Properties. Click the
Content|Classes tab. You should see an include filter for .dat
(+**/*.dat)<br>
</p>
<p><span style="font-weight: bold;">EJB JAR without the EJB designer
XML descriptors<br>
- </span>Right click the EJB module and select Properties<br>
<span style="font-weight: bold;">- </span>Click the Content|Classes
page, click the Add Filter page, click the Include button, add
the following the exclude filter:&nbsp; META-INF/ejb-modeler*.xml<br>
</p>
<p><span style="font-weight: bold;">WAR with custom descriptor(s) in
the WEB-INF directory<br>
- </span>Copy the custom descriptor(s) over to the WEB-INF directory
of the web module.<br>
Note : The descriptor should have a standard extension listed in the
XML file type (Tools|Preferences). Please add the required extension to
the global file types if it is not recognized by JBuilder. This applies
to adding custom descriptors to any J2EE module in JBuilder.<br>
</p>
<p><span style="font-weight: bold;">WAR without any classes (only
descriptors)</span><br>
- Right click the web module and select Properties. Click the
Module page and uncheck the Java Class file type.<br>
<br>
<span style="font-weight: bold;">WAR with custom class filters<br>
</span>- Right click the web module and select Properties. <br>
- Click the Module page and uncheck the Java Class file type.<br>
- Click the Content|Classes page and add include filters for the
required classes (e.g. &lt;package name&gt;/*.*)<br>
</p>
<p><span style="font-weight: bold;">WAR with custom file types<br>
</span>Note : This example adds the .inc extension to the JSP file type.<br>
- Tools|Preferences. Click the Browser|File Types page. Select JSP file
in the Recognized File Types list box.<br>
- Click the Add button. Enter inc and click OK<br>
- Right click the web module's Module Directory and select New|File.
Create a&nbsp; file named&nbsp; test1 with extension inc in the module
directory at the root level.<br>
<span style="font-weight: bold;"><br>
EAR with custom files (.dat,
archives and descriptors)<br>
</span>- Tools|Preferences. Click the Browser|File Types page.
Select Generic Resource File in the Recognized File Types list box.<br>
- Click the Add button. Enter dat and click OK<br>
- Project|Project Properties. Click the Build|Resource page. Select
dat and click the Copy button.<br>
- Right click the EAR Module and select Properties. Click the
Content|Classes page. Click the
Add Filter page, click
the Include button and add the following filter: **/*.dat<br>
<br>
<span style="font-weight: bold;">RAR with classes and dependencies </span><br>
- Right click the RAR module and select Properties. Click the
Module page and check the Java Class file type.<br>
<span style="font-weight: bold;">- </span>Click the
Content|Dependencies page and select the required libraries. Select
the option Always Include all classes and resources.<br>
<br>
<span style="font-weight: bold;">Application Client with classes and
dependencies<br>
</span><span style="font-weight: bold;">- </span>Click the
Content|Dependencies page and select the required libraries. Select
the option Always include all classes and resources.<br>
Note : This will expand the libraries into the application client JAR.<br>
</p>
<h2>Improving Module Build Performance</h2>
To improve module build performance:<br>
<ul>
  <li>Turn off file types that are not being used in the module. To do
this, right
click the module and select Properties. Then click the Module page and
uncheck file types that are not in use for the module.</li>
  <li>Turn off archive generation if the archive is not being deployed.
To do this, right click the module and select Properties. Then click
the Build page and
select Never in the drop down for Build&nbsp; archive.</li>
  <li>Turn off module synchronization for :<br>
  </li>
</ul>
<ol style="margin-left: 40px;">
  <li>non-web modules</li>
  <li>web modules if you are using servers other than Tomcat or
WebLogic.</li>
</ol>
<div style="margin-left: 40px;">To turn off module synchronization,
right click the module and select Properties. Click the Build page and
uncheck Synchronize module directory with archive content.<br>
</div>
<ul>
  <li>Remove any clean filters that are not used (for file types that
are not in use). To do this, right click the module and select
Properties. Then click
the Clean page and remove any exclude filters for file types that are
not in use for the module.</li>
</ul>
<div style="margin-left: 40px; font-weight: bold;"><span
 style="font-style: italic;">Note :&nbsp; Anything that is not excluded
using an exclude filter in the Clean page will be deleted in the clean
process. Please ensure that you add an exclude filter in the Clean page
for any custom file types that you are using in your module directory.</span><br>
</div>
<br>
In addition the following can be used specifically to improve web
module build performance:<br>
<ul>
  <li>Turn off dependencies that are not being used in the module.
Right click the module and select Properties. To do this, click the
Content|Dependencies page and select libraries that are not needed.
Select the option Never Include Classes And Resources option.</li>
  <li>Add specific filters to reduce the content of web archives. All
classes in the project's ouput path are included in the web archive by
default. </li>
</ul>
<div style="margin-left: 40px;"><br>
</div>
<p></p>
</body>
</html>