You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@uima.apache.org by cw...@apache.org on 2016/12/06 16:07:26 UTC
svn commit: r1772908 - /uima/uima-as/trunk/README
Author: cwiklik
Date: Tue Dec 6 16:07:26 2016
New Revision: 1772908
URL: http://svn.apache.org/viewvc?rev=1772908&view=rev
Log:
UIMA-5094 fixed typos, added comments about version checker updates
Modified:
uima/uima-as/trunk/README
Modified: uima/uima-as/trunk/README
URL: http://svn.apache.org/viewvc/uima/uima-as/trunk/README?rev=1772908&r1=1772907&r2=1772908&view=diff
==============================================================================
--- uima/uima-as/trunk/README (original)
+++ uima/uima-as/trunk/README Tue Dec 6 16:07:26 2016
@@ -35,6 +35,10 @@ For more details, please see http://uima
- Fixed support of AMQ white listing of packages
- Added support to disable JMX via a new argument -Duima.as.enable.jmx=false
- Fixed dd2spring issues
+ - Updated version checker to test compatibility with UIMA SDK. Code terminates
+ if UIMA-AS major version matches but a minor version of the UIMA SDK is less than
+ the minor version of UIMA-AS. The UIMA-AS runtime will work with SDK 2.9.X, 2.10.X,
+ etc but will not work with SDK 3.X.X nor SDK 2.8.X or lower.
- Other Bug fixes
@@ -350,7 +354,7 @@ Connect a jConsole to this JMX service a
Under the MBeans tab, expand org.apache.uima in the left panel to view UIMA components enabled for JMX monitoring.
NOTE:
-In case when opening an RMI port for JMX monitoring is not possile due to security concerns, you can disable
+In case when opening an RMI port for JMX monitoring is not possible due to security concerns, you can disable
JMX via optional argument -Duima.as.enable.jmx=false. With this setting, the UIMA-AS will start with no
JMX support and an RMI port will not be opened.
@@ -423,7 +427,7 @@ An example of this kind of migration is
3. JCAS caching Enable/Disable not supported in the Deployment Editor GUI.
- 4. In cases where Analysis Engine deployed in UIMA AS servic throws a user-defined exception, an
+ 4. In cases where Analysis Engine deployed in UIMA AS service throws a user-defined exception, an
application hosting UIMA AS client must include such exception class in its classpath. Otherwise,
ClassNotFoundException is thrown in the UIMA AS client while deserializing a reply.