Magnolia 4.5 reached end of life on June 30, 2016. This branch is no longer supported, see End-of-life policy.
Magnolia 4.3 brings many new features, improvements and bugfixes; here are some highlights:
The following should also be of specific interest for developers:
multipartfilter is now before the
i18nfilter is now before the
info.magnolia.objectfactory: we refactored the (now deprecated)
ClassUtilclasses into this new package. For most common usages, you can now use
Classes, respectively. This new API will possibly change in future versions, however we expect the
Classesclasses to remain stable.
FactoryUtilto get an updated instance). See MAGNOLIA-2553 for details.
NodeData) has been refactored and cleaned up. See MAGNOLIA-3015 and sub-tasks for details. A few methods have been deprecated but the changes should otherwise be transparent for most cases.
NodeDataWrapper) have been improved. We introduced a couple more useful wrappers, too. See MAGNOLIA-3020 for details.
ModuleRegistry.get*methods now throw exceptions for unknown modules; a new
isModuleRegistered()method was added to cover cases where the previous behaviour was needed. See MAGNOLIA-2762. Module instances can also be retrieved by class rather than by name.
Detailed change logs can be found in our Jira:
Many of the bundled modules have also been updated with a few bug fixes. Two new modules are now bundled with Magnolia Enterprise Edition: the Groovy module, and the Google Analytics for STK module. Those modules are also available for the Community Edition.
Lastly, we've started a preview/proposal module which prefigures a few reviewed templating mechanisms which we're hoping to finalize for Magnolia 5.0. Some details are available at MAGNOLIA-2993, on Greg's blog, and on our wiki. (to be updated)
The Magnolia team would like to thank everyone who reported issues or contributed patches to this release. Your continued 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 each version following the version you are updating from; 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 are skipping (1.2.4 and 1.2.5 in this example).
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.