You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@uima.apache.org by ea...@apache.org on 2008/03/21 14:02:19 UTC
svn commit: r639616 - in /incubator/uima/uimacpp/trunk: RELEASE_NOTES.html
buildSrcTree.cmd docs/uimacpp.dox
Author: eae
Date: Fri Mar 21 06:02:08 2008
New Revision: 639616
URL: http://svn.apache.org/viewvc?rev=639616&view=rev
Log:
UIMA-275 progress
Modified:
incubator/uima/uimacpp/trunk/RELEASE_NOTES.html
incubator/uima/uimacpp/trunk/buildSrcTree.cmd
incubator/uima/uimacpp/trunk/docs/uimacpp.dox
Modified: incubator/uima/uimacpp/trunk/RELEASE_NOTES.html
URL: http://svn.apache.org/viewvc/incubator/uima/uimacpp/trunk/RELEASE_NOTES.html?rev=639616&r1=639615&r2=639616&view=diff
==============================================================================
--- incubator/uima/uimacpp/trunk/RELEASE_NOTES.html (original)
+++ incubator/uima/uimacpp/trunk/RELEASE_NOTES.html Fri Mar 21 06:02:08 2008
@@ -1,9 +1,9 @@
<html>
<head>
- <title>Apache UIMA C++ v2.2.0 Releate Notes</title>
+ <title>Apache UIMA C++ v2.2.2 Releate Notes</title>
</head>
<body>
-<h1>Apache UIMA C++ (Unstructured Information Management Architecture) v2.2.0 Release Notes</h1>
+<h1>Apache UIMA C++ (Unstructured Information Management Architecture) v2.2.2 Release Notes</h1>
<h2>Contents</h2>
<p>
@@ -62,7 +62,7 @@
<h2><a name="major.changes">2. Major Changes in this Release</a></h2>
<p>
-This section describes what has changed between version 1.4.4 and version 2.1 of
+This section describes what has changed between version 1.4.4 and version 2.2.2 of
UIMA C++. A migration guide is provided below that describes the required updates to
your C++ code and descriptors. See Section 3, "Migrating from IBM UIMA C++ to
Apache UIMA C++".
@@ -82,7 +82,7 @@
<h3>2.2. Extended Platform Support</h3>
<p>
On 64-bit Unix platforms the Apache UIMA C++ framework can be built as
-a 64-bit library. This enabling C++, Perl, Python and Tcl analytics to
+a 64-bit library. This enables C++, Perl, Python and Tcl analytics to
fully utilize a 64-bit address space. Both XML and binary CAS
serialization formats are compatible between 32 and 64-bit builds.
</p>
@@ -92,11 +92,17 @@
<h3>2.3. Better Integration with Java SDK</h3>
<p>
-The Apache UIMA SDK will now run seamlessly with the UIMA C++ framework. Command line tools and Eclipse run configurations in the Java SDK set the native shared library path assuming the UIMA C++ SDK is installed directly under $UIMA_HOME.
+The Apache UIMA SDK shell scripts and Eclipse run configurations set native environment paths assuming the UIMA C++ SDK is installed directly under $UIMA_HOME. This enables the standard UIMA SDK tools to work seemlessly with C++ based annotators.
</p>
<p>
On Unix platforms, the UIMA C++ examples directory can be loaded as an Eclipse CDT project, supporting development of both UIMA C++ and Java components in the same Eclipse IDE.
-</p>
+</p>
+<p>
+By default, when a uimacpp annotator is instantiated from Java, the annotator runs in the JVM process with communication via the JNI. Multiple uimacpp annotators instantiated in the same JVM must share the same native environment, therefor they must share the same version UIMA C++ framework. As before, a uimacpp annotator can be isolated by wrapping it as a Vinci service.
+</p>
+<p>
+A new approach is provided in this release which allows process isolation of uimacpp annotators without wrapping each one in a JVM. When deployed from Java as a UIMA-AS service, a uimacpp annotator is spawned by the JVM as native process. The native UIMA-AS service communitates to clients via JMS messaging, completely independently of the JVM. However, the native service connects back to the JVM to enable JMX monitoring and logfile integration with other UIMA annotators running in the same JVM.
+</p>
<h3>2.4. C++ Namespace and Module Name Changes</h3>
<p>
@@ -142,7 +148,10 @@
<p>
The proposed standard for XML interchange of CAS data, XMI serialization,
is now supported by UIMA C++. The C++ application driver, runAECpp, has a new option
-to specify XMI format input files.
+to specify XMI format input files, and the output format is now XMI.
+</p>
+<p>
+XMI serialization is also key to implementing the UIMA-AS service wrapper for uimacpp-based annotators.
</p>
<h3>2.8. Building the SDK on Unix is Simplified</h3>
@@ -160,7 +169,7 @@
<h3>3.1. Migrating C++ Source Code</h3>
<p>
This section describes what source code changes are required to migrate from
-UIMA C++ version 1.4.4 to Apache UIMA C++ v2.1. Please note that the first two changes
+UIMA C++ version 1.4.4 to Apache UIMA C++ v2.2.2. Please note that the first two changes
are order dependent.
</p>
@@ -199,7 +208,9 @@
<h2><a name="more.info">6. More Documentation on Apache UIMA C++</a></h2>
<p>
-Please see <a href="docs/overview_and_setup.html">C++ Overview and Setup</a>
+Please see <a href="docs/overview_and_setup.html">Overview and Setup</a>
+for a high level overview of UIMA C++,
+and <a href="docs/html/index.html">Doxygen</a> for details on the UIMA C++ APIs.
</p>
</body>
Modified: incubator/uima/uimacpp/trunk/buildSrcTree.cmd
URL: http://svn.apache.org/viewvc/incubator/uima/uimacpp/trunk/buildSrcTree.cmd?rev=639616&r1=639615&r2=639616&view=diff
==============================================================================
--- incubator/uima/uimacpp/trunk/buildSrcTree.cmd (original)
+++ incubator/uima/uimacpp/trunk/buildSrcTree.cmd Fri Mar 21 06:02:08 2008
@@ -19,7 +19,7 @@
REM under the License.
REM For now, update version in line below
-set srcName=uimacpp-2.2.0-incubating
+set srcName=uimacpp-2.2.2-incubating
REM check args
if "%~1" == "" (
Modified: incubator/uima/uimacpp/trunk/docs/uimacpp.dox
URL: http://svn.apache.org/viewvc/incubator/uima/uimacpp/trunk/docs/uimacpp.dox?rev=639616&r1=639615&r2=639616&view=diff
==============================================================================
--- incubator/uima/uimacpp/trunk/docs/uimacpp.dox (original)
+++ incubator/uima/uimacpp/trunk/docs/uimacpp.dox Fri Mar 21 06:02:08 2008
@@ -40,7 +40,7 @@
# This could be handy for archiving the generated documentation or
# if some version control system is used.
-PROJECT_NUMBER = "v2.2.0"
+PROJECT_NUMBER = "v2.2.2"
# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
# base path where the generated documentation will be put.