This document describes the steps needed to upgrade the edoras one application to 1.5.0.S111.
Please stop the edoras one server, perform all upgrade steps described below and then restart the server again at the end.
Caching of system groups in a clustered installation
The system groups provided by the GroupService.getSystemGroups()
method are now cached using the distributed Redis cache
when the clustering Spring profile cache-redis
is enabled, allowing clustered installations to evict the cache entries across
the cluster.
Spring configuration
DefaultConfigurableContentManager bean configuration
The transaction manager reference has been removed from the DefaultConfigurableContentManager constructor. DefaultConfigurableContentManager bean definitions in your project will have to be updated to remove the transaction manager reference.
CMMN bean configurations
The constructors for a number of CMMN beans defined in the edoras one files cmmn-engine-context.xml
and test-cmmn-engine-context.xml
have been changed. Normally these bean definitions are provided
by the base edoras one configuration, but if you have overwritten them in your project then your
configuration will also have to be updated.
Security configuration
The configuration of the browserRedirectionFilter
bean has been simplified. This bean is responsible for
preserving the location from an incoming link around the edoras one login process. Now only a pattern for the
login page needs to be specified, and no explicit application context is required:
<bean id="browserRedirectionFilter" class="com.edorasware.cloud.filter.BrowserRedirectionFilter"> <property name="loginPageUrlPattern" value="(.*)/login.jsp"/> </bean>
Some additional login configurations were also copied from the main security configuration into the separate login page configurations. This was done to avoid warnings on system startup. If you override the default security configuration from the bootstrap project or have your own security configuration then you should make the corresponding changes.
Frontend project setup improvements
As stated in the release notes, we upgraded the project setup for customers who override the following default edoras one HTML pages:
-
index.html
-
case.html
-
embedded.html
-
nomenu.html
If you override any of the above mentioned HTML files then please follow the following steps in order to adapt them accordingly:
-
Change the following resource URIs in the overwritten HTML file from the current value to the value defined after the
→
:-
./forms/app/fms.files-1.5.0.S111.js → ./forms/app/fms.files.js
-
./one/app/one.files-1.5.0.S111.js → ./one/app/one.files.js
-
./one/less/main-1.5.0.S111.min.less → ./one/less/main.less
-
./view-engine/app-{HASH}.js → ./view-engine/app.js
-
./view-engine/app-{HASH}.css → ./view-engine/app.js
-
-
After these changes, the above mentioned resources should be included in your HTML in the following way:
<script type="text/javascript" src="./forms/app/fms.files.js"></script> <script type="text/javascript" src="./one/app/one.files.js"></script> <link type="text/css" media="all" href="./one/less/main.less" rel="stylesheet/less"/> <script type="text/javascript" src="./view-engine/app.js"></script> <link rel="stylesheet" type="text/css" media="all" href="./view-engine/app.css"/>
-
Next you need to adapt the
web.xml
by adding the following filter:
<filter> <filter-name>linkedResourcesFilter</filter-name> <filter-class>org.springframework.web.filter.DelegatingFilterProxy</filter-class> </filter> <filter-mapping> <filter-name>linkedResourcesFilter</filter-name> <url-pattern>/*</url-pattern> </filter-mapping>
It is important that the linkedResourcesFilter
is added after the viewEngineScriptFilter
.
These resource imports do not need to be changed any further in the upcoming releases as they should remain stable. This way, changing the hashed and versioned names of the resources is not needed when upgrading to a newer version of edoras one.
Bootstrap project
Here you will find a list of files which have changed in the bootstrap project 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/content-config.xml
-
removed the transaction manager from the content manager constructor
-
src/main/resources/com/edorasware/bootstrap/config/security/security-basic-config.xml
-
updated the security configuration
-
src/main/resources/com/edorasware/bootstrap/config/one.properties
-
adding property
system.linked.resources.mapping.files
a comma separated list of the mapping files which are used to link the front end resources -
src/main/resources/com/edorasware/acme/config/acme-context.xml
-
moved system groups cache to Redis if a cluster is used
-
src/main/resources/com/edorasware/acme/palette/acme.process.palette.xml
-
xsd version update in the palette
-
src/main/webapp/WEB-INF/web.xml
-
linkedResourcesFilter
was added.