releasenotes.html

SAP ERP的二次开发

</table></div>
</td></tr>

<tr><td valign="top" align="left">&nbsp;</td></tr>
<tr><td valign="top" align="left"><SPAN class=head>Bugfix in treatment of connection properties</SPAN></td></tr>
<tr><td valign="top" align="left">
<div class="textblack"><table cellSpacing=0 cellPadding=2 border=0>
    <tr><td class="faqw">
        Some connection properties might have been misinterpreted as
        boolean values and/or leading spaces were ignored. This led to
        log on failures.
    </td></tr>
</table></div>
</td></tr>

<tr><td valign="top" align="left">&nbsp;</td></tr>
<tr><td valign="top" align="left"><SPAN class=head>Bugfix in JCO.Client.execute()</SPAN></td></tr>
<tr><td valign="top" align="left">
<div class="textblack"><table cellSpacing=0 cellPadding=2 border=0>
    <tr><td class="faqw">
        Uninitialized function parameters were sent to the SAP system filled with their default values
        or in some cases with their initial values.<br>
        This prevented the SAP system from setting its own default values on the backend side and could
        have affected the result of the called function module.
        <em>Note:</em> This bug is only known in JCo 2.1.3.
    </td></tr>
</table></div>
</td></tr>

<tr><td valign="top" align="left">&nbsp;</td></tr>
<tr><td valign="top" align="left"><SPAN class=head>Bugfix in treatment of JCO.Request and JCO.Response</SPAN></td></tr>
<tr><td valign="top" align="left">
<div class="textblack"><table cellSpacing=0 cellPadding=2 border=0>
    <tr><td class="faqw">
        When using the <tt>JCO.Request</tt> and <tt>JCO.Response</tt> model the content of simple parameters
        could have been lost if the called function module contained tables in its table parameter list.
    </td></tr>
</table></div>
</td></tr>

<tr><td valign="top" align="left">&nbsp;</td></tr>
<tr><td valign="top" align="left"><SPAN class=head>Bugfix in event firing for ServerStateChangedListener</SPAN></td></tr>
<tr><td valign="top" align="left">
<div class="textblack"><table cellSpacing=0 cellPadding=2 border=0>
    <tr><td class="faqw">
        The server state change event when changing from state busy to not busy will now be fired to the
        <tt>JCO.ServerStateChangedListener</tt>s after the data in the <tt>JCO.Throughput</tt> has been set -
        and not before as it was previously.
    </td></tr>
</table></div>
</td></tr>

<tr><td valign="top" align="left">&nbsp;</td></tr>
<tr><td valign="top" align="left">&nbsp;</td></tr>
<tr><td valign="top" align="left"><SPAN class=head>Release Notes 2.1.3</SPAN></td></tr>
<tr><td valign="top" align="left"><HR class="separator" noshade></td></tr>

<tr><td valign="top" align="left">&nbsp;</td></tr>
<tr><td valign="top" align="left"><SPAN class=head>New codepage supported</SPAN></td></tr>
<tr><td valign="top" align="left">
<div class="textblack"><table cellSpacing=0 cellPadding=2 border=0>
    <tr><td class="faqw">
        The SAP codepage 1810 (Hebrew with LTR [Left-to-Right] and RTL [Right-to-Left] mark) is
        additionally supported now.
    </td></tr>
</table></div>

<tr><td valign="top" align="left">&nbsp;</td></tr>
<tr><td valign="top" align="left"><SPAN class=head>Improvement of the internal XML Parser</SPAN></td></tr>
<tr><td valign="top" align="left">
<div class="textblack"><table cellSpacing=0 cellPadding=2 border=0>
    <tr><td class="faqw">
    The internal XML Parser was extended to parse the predefined XML entity &amp;apos; (') as
    required by W3C Recommendation for XML 1.0 in
    "<a href="http://www.w3.org/TR/REC-xml">4.6 Predefined Entities</a>".
    Other predefined XML entities are the HTML entities and will be parsed since 2.1.2.
    </td></tr>
</table></div>

<tr><td valign="top" align="left">&nbsp;</td></tr>
<tr><td valign="top" align="left"><SPAN class=head>Bugfix in handling inactive tables in JCO.Client</SPAN></td></tr>
<tr><td valign="top" align="left">
<div class="textblack"><table cellSpacing=0 cellPadding=2 border=0>
    <tr><td class="faqw">
        A crash in the JCo native part could occur, if some tables in the table parameter list were
        marked as inactive.
        <em>Note:</em> This bug is only known in JCo 2.1.2.
    </td></tr>
</table></div>

<tr><td valign="top" align="left">&nbsp;</td></tr>
<tr><td valign="top" align="left"><SPAN class=head>Bugfix in JCo's initialization routine</SPAN></td></tr>
<tr><td valign="top" align="left">
<div class="textblack"><table cellSpacing=0 cellPadding=2 border=0>
    <tr><td class="faqw">
    JCo could not load its JNI runtime library from the same directory where the <tt>sapjco.jar</tt>
    file or the JCo class files are located, if this directory name contains spaces or non-ascii letters
    and JDK 1.4 was used.
    </td></tr>
</table></div>

<tr><td valign="top" align="left">&nbsp;</td></tr>
<tr><td valign="top" align="left">&nbsp;</td></tr>
<tr><td valign="top" align="left"><SPAN class=head>Release Notes 2.1.2</SPAN></td></tr>
<tr><td valign="top" align="left"><HR class="separator" noshade></td></tr>

<tr><td valign="top" align="left">&nbsp;</td></tr>
<tr><td valign="top" align="left"><SPAN class=head>Added new chapter "Configuration" to documentation</SPAN></td></tr>
<tr><td valign="top" align="left">
<div class="textblack"><table cellSpacing=0 cellPadding=2 border=0>
    <tr><td class="faqw">
    A new chapter "Configuration" has been added to the JCo documentation. Please see the appropriate
    link on the left menu bar.
    </td></tr>
</table></div>

<tr><td valign="top" align="left">&nbsp;</td></tr>
<tr><td valign="top" align="left"><SPAN class=head>Added new API JCO.getMiddlewarePropertyInfo()</SPAN></td></tr>
<tr><td valign="top" align="left">
<div class="textblack"><table cellSpacing=0 cellPadding=2 border=0>
    <tr><td class="faqw">
    Returns information about the properties that are offered by the middleware implementation.
    Each element of the array is a set of two <tt>Strings</tt> containing the name and description of
    a middleware property.
    </td></tr>
</table></div>

<tr><td valign="top" align="left">&nbsp;</td></tr>
<tr><td valign="top" align="left"><SPAN class=head>Bugfix in JCO.Table.toString()</SPAN></td></tr>
<tr><td valign="top" align="left">
<div class="textblack"><table cellSpacing=0 cellPadding=2 border=0>
    <tr><td class="faqw">
        The method <tt>JCO.Table.toString()</tt> threw an <tt>ArrayIndexOutOfBoundsException</tt> if
        the table contained only one unnamed column (vector).
    </td></tr>
</table></div>

<tr><td valign="top" align="left">&nbsp;</td></tr>
<tr><td valign="top" align="left"><SPAN class=head>Bugfix in the handling of JCO.AbapException</SPAN></td></tr>
<tr><td valign="top" align="left">
<div class="textblack"><table cellSpacing=0 cellPadding=2 border=0>
    <tr><td class="faqw">
    In some rare cases when the backend system sent an application exception, JCo set the ABAP exception
    key and text without previuously cleaning the last exception texts. This led to a corrupted exception
    key and message text.
    </td></tr>
</table></div>

<tr><td valign="top" align="left">&nbsp;</td></tr>
<tr><td valign="top" align="left"><SPAN class=head>Bugfix for state handling in JCO.Server</SPAN></td></tr>
<tr><td valign="top" align="left">
<div class="textblack"><table cellSpacing=0 cellPadding=2 border=0>
    <tr><td class="faqw">
    After calling <tt>suspend()</tt> the server thread could not be stopped or restarted again. Furthermore
    calling the server's <tt>suspend()</tt> or <tt>stop()</tt> method had no effect while it was currently
    dispatching a request.
    </td></tr>
</table></div>

<tr><td valign="top" align="left">&nbsp;</td></tr>
<tr><td valign="top" align="left"><SPAN class=head>Bugfix for deadlock in JCO.Server</SPAN></td></tr>
<tr><td valign="top" align="left">
<div class="textblack"><table cellSpacing=0 cellPadding=2 border=0>
    <tr><td class="faqw">
    A deadlock could have occurred between an application thread invoking the <tt>JCO.Server.start()</tt>
    or <tt>JCO.Server.stop()</tt> methods and a server thread, when the server thread was firing
    <tt>serverStateChange</tt> events and the invoked listener used the server instance as a lock object.
    </td></tr>
</table></div>

<tr><td valign="top" align="left">&nbsp;</td></tr>
<tr><td valign="top" align="left"><SPAN class=head>Bugfix of the internal XML Parser</SPAN></td></tr>
<tr><td valign="top" align="left">
<div class="textblack"><table cellSpacing=0 cellPadding=2 border=0>
    <tr><td class="faqw">
    The internal XML Parser catched, traced and swallowed all runtime errors. This could lead to an
    unnoticed inconsistent state in JCo tables or structures.<br>
    Only JCo version 2.1.1 was affected by this bug.
    </td></tr>
</table></div>

<tr><td valign="top" align="left">&nbsp;</td></tr>
<tr><td valign="top" align="left"><SPAN class=head>Improvement of the internal XML Parser</SPAN></td></tr>
<tr><td valign="top" align="left">
<div class="textblack"><table cellSpacing=0 cellPadding=2 border=0>
    <tr><td class="faqw">
    The internal XML Parser can now parse all HTML entities defined with the HTML 4 Specification chapter
    "<a href="http://www.w3.org/TR/html401/sgml/entities.html">Character entity references in HTML 4</a>".
    </td></tr>
</table></div>

<tr><td valign="top" align="left">&nbsp;</td></tr>
<tr><td valign="top" align="left"><SPAN class=head>Bugfix avoiding crashes in native part</SPAN></td></tr>
<tr><td valign="top" align="left">
<div class="textblack"><table cellSpacing=0 cellPadding=2 border=0>
    <tr><td class="faqw">
    A crash in the JCo native part could occur, if there were incompatible structure or table metadata
    defined on the local and the backend side.<p>
    <em>This bugfix <b>only avoids</b> the crash. It is still neccessary
    to correct the repository's metadata, otherwise the transferred parameter data will be garbled.</em>
    </td></tr>
</table></div>

<tr><td valign="top" align="left">&nbsp;</td></tr>
<tr><td valign="top" align="left"><SPAN class=head>New APIs in JCO.Record</SPAN></td></tr>
<tr><td valign="top" align="left">
<div class="textblack"><table cellSpacing=0 cellPadding=2 border=0>
    <tr><td class="faqw">
        New APIs <tt>setValue(char[] value, int index)</tt>, <tt>setValue(char[] value, String name)</tt>,
        <tt>getCharArray(int index)</tt> and <tt>getCharArray(String name)</tt> have been added.
    </td></tr>
</table></div>

<tr><td valign="top" align="left">&nbsp;</td></tr>
<tr><td valign="top" align="left"><SPAN class=head>Improved method JCO.ParameterList.setActive()</SPAN></td></tr>
<tr><td valign="top" align="left">
<div class="textblack"><table cellSpacing=0 cellPadding=2 border=0>
    <tr><td class="faqw">
        JCo now allows to set every table or structure in the export and table parameters lists as
        inactive (except flat structures) if it is irrelevant for a specific RFC call. The content
        of inactive parameters won't be marshalled to JCo's native layer and their content won't be
        sent to the backend system thus increasing the performance of the given RFC call.
    </td></tr>
</table></div>

<tr><td valign="top" align="left">&nbsp;</td></tr>
<tr><td valign="top" align="left"><SPAN class=head>Bugfix in JCO.Record.copyFrom()</SPAN></td></tr>
<tr><td valign="top" align="left">
<div class="textblack"><table cellSpacing=0 cellPadding=2 border=0>
    <tr><td class="faqw">