LexEVS 6.5.0 CTS2 Overview of Changes
LexEVS 6.5.0 CTS2 release consisted of the following changes:
- Update to Java 1.8
- Update to Tomcat 8
- Update to MySQL 5.6
- OS upgrade to CentOS 7
- The removal of all legacy caCORE Data Services including QBE, Soap and REST services from the LexEVS Remote API.
Default Number of Entries to Return
In LexEVS 6.5.0, the number of entries in each REST service call can be controlled from a properties file. The wepapp-config.properties file has the ability to set how many entries to return for each call. If there are more entries than this number, then the return call passes along additional links to retrieve the next/previous pages.
This includes, calls to entities, value sets, associations, etc. If this property is not specified in the wepapp-config.properties or passed in via the REST URL, the internal default is 50.
The maxToReturn parameter has been set to 1000 in the wepapp-config.properties. All REST calls will return up to 1000 entries for each call.
The end user can override this value by passing it in via the REST URL.
Examples:
No maxToReturn value set in the URL. This will use the value set in wepapp-config.properties file, 1000.
maxToReturn value is set in the URL to 20. This overrides the value in the properties file.
CTS2 REST Services over HTTPS
With the upgrade to CTS2 REST services over HTTPS, you may get an error when querying the LexEVS CTS2 Service using Java 8 due to cryptography incompatibilities between the client and the server.
This can be resolved by downloading the extended JCE files from Oracle (Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files 8 Download) at http://www.oracle.com/technetwork/java/javase/downloads/jce8-download-2133166.html.
This fixes CTS2 REST service calls from a Java 8 client.
