 |
Page History
...
LexEVS 6.4.2 refers not only to the LexEVS Java API code base, but also supporting and extended services for LexEVS. This includes the CTS2 Framework, the LexEVS CTS2 REST service, the LexEVS Remote API, and the URI Resolver service.
End User API Migration
:LexEVS RMI Java client code will, in almost all cases, have to be updated to Java 8
Users already working with 6.4.1 Remote Java API will need to update to 6.4.2 compatible client jars including:
- LexEVS lexbig.jar
- LexEVSSecurity.jar,
- lexevsapi64-beans.jar
- lexevsapi64-framework.jar
End User REST / Data Service Migration
:LexEVS will be dropping support for the caCORE service model and the services that are part of this model. These include the GetXML, GetHTML and similar Query by Example (QBE) services that were provided by the inclusion of caCORE into LexEVS. Legacy Data Service users will have to transition to the CTS2 REST API. A mapping from caCORE REST XML output to CTS2 REST XML output will be provided.
...
Support
LexEVS will be maintaining dual servers for a period of time to allow people to migrate from earlier versions to 6.4. The date of the sunsetting of older versions has not been set and will depend on user feedback. If you have any concerns, questions or comments please contact us at:
Server-side changes
:This code base has been confirmed to support recent CBIIT tech stack updates including:
- CentOS 7
- MySQL 5.6
...
