The focus on this release upgrades is the content manager cache. The other changes which can affect product behavior are byte range requests and application import refactoring.
For the detailed information see chapters below.
Byte range requests
There is a change in the behaviour of the HTTP connections due to introduction the byte-range request support. More (smaller) HTTP requests may happen instead of less frequent (heavier) ones. Check the capabilities of your system in terms of number of concurrent open connections.
It is recommended to clean up your temporary directory of converted documents. The documents converted with the previous versions are not linearized by default.
Content manager cache
The new configuration for the content manager cache involves changes in the redis cache format. The redis database must be flushed before the upgrade.
To apply cacheDir
property stop the server, remove the content of contentProvider.tempDir
, set the proper value to cacheDir
property and start the server again.
${cacheDir}/coverted-content
directory will be created to store cached converted content files.
App import refactoring
A first step was taken in this release to simplify the App import code. Although runtime code is very unlikely to be affected by these changes, some test code in customer projects may use the App import functionality to load test Apps. If this is the case the following changes may need to be made:
-
the AppReaderFactory interface has been removed. Instead of using a factory to create an AppReader instance, simply autowire the AppReader directly into the test class.
-
the AppReader creates an AppContent object, which can be passed to the app importer as the first parameter
A sample test would therefore look something like the following:
public class MyTestClass {
@Autowired
private AppReader appReader;
@Test
public void importTest() throws Exception {
...
AppContent appContent = this.appReader.getAppContent(appFile);
this.appImporter.importApp(appContent, null, true, false, false, TEST_COMMENT);
...
}
}
Miscellaneous
Bootstrap project
Here you will find a list of files which have changed since the last release. This helps you check the difference between your bootstrap project version and the current one:
/src/main/resources/com/edorasware/bootstrap/config/one.properties
: cacheDir
property was introduced and document configuration was re-added
/src/main/webapp/custom.css
: an example was added
src/edoras-one-bootstrap/src/main/resources/com/edorasware/bootstrap/config/content-config.xml
: deprecatedContentProvider
bean was added again