📄 jbx_update_4.html
字号:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
<html>
<head>
<meta name="Author" content="JBuilder Release Team">
<style>
BODY {
background-color : White;
color : Black;
}
H2.highlight {
color : Navy;
}
H4 {
color : Grey;
}
UL LI {
list-style-type : square;
padding-bottom : 12px;
}
OL LI {
list-style-type : decimal;
}
.compact {
padding-bottom : 0px;
}
.center {
text-align : center;
}
.leading {
padding-bottom : 12px;
}
.super {
font-size : xx-small;
vertical-align : super;
}
</style>
<title>Borland JBuilder X Update 003: Release Notes</title>
</head>
<body>
<div class="center">
<h1>Borland JBuilder X Update 004 <br>
Release Notes</h1>
<p><strong>This software patch is being provided to licensed users of Borland
JBuilder X. <br>
Installation and use is governed by the license statement for Borland JBuilder
X.</strong></p>
<p><strong>This patch is intended for all supported platforms and languages
for JBuilder X. Some strings displayed by the patch may be displayed in English,
even if you are using a localized version of JBuilder X.</strong></p>
</div>
<p>For more information about JBuilder, including FAQs and workarounds, please
visit the <a href="http://www.borland.com/devsupport/jbuilder/">JBuilder Developer
Support</a>
web site. If you have a problem, please report it via the <a href="http://qualitycentral.borland.com/">
Bug Submission Form</a>
. Please be sure to include steps to reproduce, source code to help reproduce
the problem and the exact text of any error messages encountered.</p>
<h2 class="highlight">Installation Instructions</h2>
<p>Read all the instructions through once before applying the update. The
following description assumes that JBuilder X has been installed in the directory
<code>\JBuilderX</code>. If you have installed JBuilder in a different directory,
substitute the one that you used. Unix users should substitute a simple (forward)
slash ("/") wherever a backslash ("\") appears in a path name.</p>
<p>This patch is delivered as one ZIP file (<code>jbx_patch_004.zip</code>
) and Release Notes.</p>
<p>To install the patch:</p>
<ol>
<li>If JBuilder is running, exit JBuilder.</li>
<li>Remove any and all other JBuilder X updates (<code>jbX*.jar</code>
) from your <code>JBuilderX\patch</code> directory.</li>
<li>Copy the patch ZIP file (<code>jbx_patch_004.zip</code>) to a local
directory.</li>
<li>Make a backup of <code>lib\javac.jar</code> and <code>lib\unittest.jar</code>
. (<strong>Note:</strong> It is recommended that you move these to a separate
directory so that they are not included in your class path.)</li>
<li>Unpack the ZIP file into your <code>JBuilderX</code> installation.
This should:
<ul>
<li class="compact">Copy <code>javac.jar</code> into your <code>JBuilderX\lib</code>
directory</li>
<li class="compact">Copy <code>unittest.jar</code> into your <code>JBuilderX\lib</code>
directory</li>
<li class="compact">Copy <code>jbX_all.jar</code>, <code>jbX_me.jar</code>
, and <code>jbX_ws.jar</code> into your <code>JBuilderX\patch</code> directory.</li>
</ul>
</li>
<li>Restart JBuilder.</li>
</ol>
<p><strong>Note:</strong> If your operating system does not have a utility
for unarchiving ZIP files, you can use the JAR utility in the JDK to unarchive
ZIP files. At the command line, change to the directory where you installed
JBuilder X, and enter the following command (where <code><jdk></code>
is the directory in which the JRE or SDK is installed) for your platform
to extract the files.</p>
<ul>
<li><strong>Windows:</strong> <code> <jdk>\bin\jar -xvf
jbx_patch_004.zip</code> </li>
<li><strong>Unix:</strong> <code> <jdk>/bin/jar -xvf jbx_patch_004.zip</code>
</li>
</ul>
<h3>File List</h3>
<p>In addition to this document, the update consists of the following files:</p>
<table border="1" cols="2" width="50%" bgcolor="Ivory" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<th align="Left">File Name</th>
<th align="Center">Size</th>
</tr>
<tr>
<td><code>javac.jar</code></td>
<td align="Right">427,461 bytes</td>
</tr>
<tr>
<td><code>jbX_all.jar</code></td>
<td align="Right">2,558,969 bytes</td>
</tr>
<tr>
<td><code>jbX_me.jar</code></td>
<td align="Right">59,631 bytes</td>
</tr>
<tr>
<td><code>jbX_ws.jar</code></td>
<td align="Right">33,404 bytes</td>
</tr>
<tr>
<td><code>unittest.jar</code></td>
<td align="Right">41,049 bytes</td>
</tr>
</tbody>
</table>
<br class="leading">
<hr>
<h2 class="highlight">Specific Fixes</h2>
<p>This patch contains fixes in the following areas:</p>
<ul>
<li class="compact"><a href="#General">General</a>
</li>
<li class="compact"><a href="#EJB_Development">EJB Development</a>
</li>
<li class="compact"><a href="#Web_Development">Web Development</a>
</li>
<li class="compact"><a href="#Build_System">Build System: EJBs and JSPs</a>
</li>
<li class="compact"><a href="#Web_Services">Web Services</a>
</li>
<li class="compact"><a href="#Mobile_Development">Mobile Development</a>
</li>
<li class="compact"><a href="#Refactoring">Refactoring</a>
</li>
<li class="compact"><a href="#Debugger">Debugger</a>
</li>
<li class="compact"><a href="#Editor">Editor</a>
</li>
<li class="compact"><a href="#Team_Development">Team Development</a>
</li>
<li class="compact"><a href="#Runtime_Systems">Runtime System</a>
</li>
<li class="compact"><a href="#Unit_Test">Unit test</a>
</li>
<li class="compact"><a href="#Visual_Cafe_Importer">Visual Cafe Importer</a>
</li>
<li class="compact"><a href="#Together">Together Studio</a>
</li>
</ul>
<br class="leading">
<hr>
<h2><a name="General"></a>
General</h2>
<ul>
<li>[184820] It is easy to undock the Project pane such that its title
bar is off the screen, making it impossible to move.</li>
<li>[186070] The splitter between the Diagram component and the Editor
component cannot be selected by choosing View|Select Browser Splitter.</li>
<li>[188552] A <code>ClassCastException</code> is thrown when getting
the <code>for</code> loop block with no curly braces.</li>
<li>[193064] It is easy to undock a Project pane such that its title bar
is off the screen. When this happens, there is no way to move it without having
to abandon that workspace.</li>
<li>[193111] Changing the type of a <code>JomField</code> (which is a
multiple-dimension array definition), leaves a character behind in the generated
source.</li>
<li>[197126] A project activation event is not being fired during JBuilder
startup if the active project is in a project group. This disables (until
another project is activated) some behaviors in the Content Manager which
depend on this, plus prevents the active personality from being set.</li>
<li>[197901] Two new menu items on the Project menu, Import Filters and
Export Filters, let the user save and import their package filter settings.
So, for example, if multiple users wanted to share the same package filters,
one user could export the filters to file and check it in with the rest of
the project. The other users can than import the package filters from that
file. Currently, when importing filters, the existing filters are overridden
with no notification to the user.</li>
<li><br>
<br>
</li>
</ul>
<h2><a name="EJB_Development"></a>
EJB Development</h2>
For additional information on building J2EE modules, please see "<a href="JBX-J2EEBuild.html">
Building J2EE Modules</a>
".
<h3>General</h3>
<ul>
<li>[185353] Adding a non-persistent field to a CMP 1.1 entity bean, and
then forcing a commit, converts it to a CMP field.</li>
<li>[186856] Changing a variable name does not properly detect the context
variable by type instead of name. This prevents the EMT from catching JBuilders
code style, Togethers code style, and any other coding style.</li>
<li>[186073] Changing interfaces in the DD editor and switching back
to the EJB Designer causes parse errors.</li>
<li>[187020] Connector module dependencies are not included in the RAR
built for an EJB module.</li>
<li>[188613] <code>cmp-version</code> is written to <code>ejb-jar.xml</code>
for a BMP 2.0.</li>
<li>[193100] When the CMP 2.0 Entity bean which is being referenced by
a session bean is renamed, the local and home interface names of the <ejb-local-ref>
tag in the <code>ejb-jar.xml</code> are not updated.</li>
<li>[193244] When an EJB contains a method that has local home interface,
there is a compilation error after a session facade is created using the Launch
DTO/SessionFacade wizard.</li>
<li>[191251] When importing a database, the table columns should not sorted
at structure pane.</li>
<li>[193367] When you add a new method or change the signature of a method
on a EJB in the EJB Designer, JBuilder sets the JNDI name back to the default
JBuilder-generated name for the EJB.</li>
<li>[193815] An incorrect <code>return</code> statement is generated
for an entity bean with a primary key type <code>java.lang.String</code>.</li>
<li>[194176] Add the following DB data type to Java type mapping:
<pre>NCHAR - String<br>NVARCHAR - String<br></pre>
It gets mapped to <code>Object</code> by default.</li>
<li>[194177] The Table Reference editor dialog does not save changes when
mapping a relationship using the default cross table.</li>
<li>[194244] Changes are not saved to <code>jndi-defintions.xml</code>
when adding a data source manually and setting properties choosing Edit
Data Source Properties.</li>
<li>[194561] When launching the DTO/Facade Wizard on a bean with many
fields, the code generated in the file <code><em>xxx</em>DtoAssember.java</code>
is truncated.</li>
<li>[194731] The EJB reference is removed when the name of the referenced
bean is changed.</li>
<li>[195460] Building an application module includes all java classes
in the resultant EAR.</li>
</ul>
<h3>WebSphere</h3>
<p><strong>Note:</strong> You will need to configure the server in JBuilder
again after applying this patch.</p>
<ul>
<li>[187484] When adding a field to a CMP that was created by selecting
a table, JBuilder stops working--you have to kill the process to exit JBuilder.</li>
<li>[187657] A <code>ClassCastException</code> is thrown when reading
<code> ejb-jar.xml</code> that contains a message-driven bean.</li>
<li>[187693] Application client only: When creating a module using existing
code, the JNDI names are not read.</li>
<li>[187696] When creating an EJB Module from existing descriptors, the
CMP descriptors are not read.</li>
<li>[187783] When creating an EJB module using existing code, some of
the existing settings in the server-specific deployment descriptor are lost.</li>
<li>[187804] When creating a module using existing code, the existing
server-specific deployment descriptor is not fully preserved.</li>
<li>[191747] Should add a data type alias:
<pre>Database Vendor Type --- *<br>Data Type --- INT<br>Data Type Alias --- INTEGER<br></pre>
</li>
<li>[191855] The EJB Designer cannot be opened without corrupting the
deployment descriptor when it includes beans that contain relationships.</li>
<li>[191872] Incorrect settings are stored in the deployment descriptor
for transactions.</li>
<li>[193242] Creating a Struts client using the DTO/Session Facade
wizard for a WebSphere 5.0 EJB module renders JBuilder unstable.</li>
<li>[195062] If a table column joins an EJB CMP relationship, but not
as a CMP field, then the EJB module cannot be built, resulting in a mapping
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -