Magnolia 4.5 reached end of life on June 30, 2016. This branch is no longer supported, see End-of-life policy.
This is a bugfix release, fixing the following:
We also bundle a new version of the DMS (1.4.2) and Packager (4.0.3).
Detailed change logs can be found in 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.
Please refer to the general update procedure page.
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.
There 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.jar file. See MAGNOLIA-2577 for technical details.
If you get exception messages such as
org.jboss.xb.binding.JBossXBException: Failed to create a new SAX parser and/or
java.lang.ClassCastException: org.apache.xerces.parsers.XIncludeAwareParserConfiguration, this is the issue you're hitting.
When 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.sh of Weblogic and add
commons-lang-2.4.jar to the
PRE_CLASSPATH. Since version 2.4 of
commons-lang doesn'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.
The imaging module doesn't function properly due to conflict with a
javax.imageio plugin bundled with this version of Weblogic. There is currently no known workaround for the issue.
Please see the list of known issues in the administration section for more details.