Maintaining Rice Version Backwards Compatibility
Summary
Add summary hereThe main requirement for the Rice client applications to maintain Rice version compatibility is that the client applications always include the version number for the version the imbedded Rice server is running when sending requests to the Central Rice server and when using the APIs/Framework to access the database directly.
The client application must include the jars that match the version of the central Rice server so that the APIs/Framework modules used will be able to properly access the information/processes on the central Rice server and in turn it can return information that appropriately corresponds to the embedded Rice version.
| No Format | ||
|---|---|---|
| ||
Version Compatibility with Embedded Implementation
Embedded Rice is version 2.1.2, Rice Services is version 2.2.1
Embedded Rice will use 2.1.2.war and jars from 2.2.1 and pass version 2.1.2 into all Rice requests.
|
...