Release notes for Magnolia 4.0.2
- What has changed since Magnolia 4.0.1
- How to update from Magnolia 4.0.1
- How to update from an earlier version of Magnolia
- Known issues
What has changed since Magnolia 4.0.1This is a bugfix release, fixing a few bugs related to cache, nodes ordering during activation and Safari 4 and Chrome compatibility. It is a recommended update for all users of Magnolia 4.0.x. As usual, the complete list of changes can be found on our Jira.
The Magnolia team would like to thank everyone who reported issues or contributed patches to this release. Your continuous interest helps us make Magnolia better.
How to update from Magnolia 4.0.1Please refer to the general update procedure page.
How to update from an earlier version of MagnoliaPlease refer to the release notes for Magnolia 4.0.1. The procedure is identical.
Please see the release notes pages for update instructions specific to the version you are updating to. If you're skipping versions (if you're updating from a fictional 1.2.3 to 1.2.6, for example), please read all release notes concerning the versions you're skipping too.
TemplatesWhen updating from a Magnolia version older than 4.0, there is a known issue related to the update of templates, for which you will need to manually fix the
templatePathproperty. After an update from Magnolia 3.6.x, these are incorrectly moved under a
parameterssubnode. Please see MAGNOLIA-2809 for details.
JBoss 5There is an unfortunate issue, specifically when deploying under JBoss 5: you will need to remove the Xerces jar from the Magnolia webapps: if deploying using war files, you can remove it from the archive, or with the following Unix command
zip -d path-to-magnolia.war WEB-INF/lib/xercesImpl-2.8.1.jar. If deploying using an exploded directory, simply remove the
WEB-INF/lib/xercesImpl-2.8.1.jarfile. See MAGNOLIA-2577 for technical details. If you get exception messages such as
org.jboss.xb.binding.JBossXBException: Failed to create a new SAX parserand/or
java.lang.ClassCastException: org.apache.xerces.parsers.XIncludeAwareParserConfiguration, this is the issue you're hitting.
WebSphereWhen installing on WebSphere, the Derby database is no longer supported due to an issue between Derby and JackRabbit on WebSphere. Please make sure to update the default configuration to use another PersistenceManager than the Derby one. There is also an issue with Lucene 2.3.0 with WebSphere 6. For this reason it is necessary to replace
WEB-INF/lib/lucene-2.3.0.jar, which is distributed with JackRabbit by default, with
WEB-INF/lib/lucene-2.2.0.jarwhich works fine.
Weblogic 10When deploying on Weblogic 10, there is a version conflict while using
commons-lang. While Weblogic-10 is distributed with
commons-lang-2.3.jar, JackRabbit and Magnolia need at least
commons-lang-2.4.jar. To resolve this issue, modify
setDomainEnv.shof Weblogic and add
PRE_CLASSPATH. Since version 2.4 of
commons-langdoesn't remove any methods, but only adds new API and fixes known bugs, there is no adverse effect from this change to the Weblogic installation.
Please see the list of known issues in the administration section for more details.