Magnolia 3.5 Community Edition (final) has been released. About 400 issues as documented in jira have been worked on for this release. We choose to significantly improve the foundation on which we build the future of Magnolia, which makes this quite a technology-focused release.
Magnolia CE 3.5 is available for immediate download from Sourceforge.
Major areas of work for this release have been:
Update / Install
We added a new installation and updating GUI. The main
feature is the update mechanism, which allows seamless
updates from 3.0.5 to the new and any future versions. The
same mechanism is used for the modules, so custom projects
will highly benefit from that feature, as you can easily
deploy new versions of your custom project/module on the
We added a basic mechanism for i18n content if you want a
1:1 structure for all the languages and not completely
separated hierarchies. Custom implementations are now
pluggable and we will improve that feature for the next
Beans for Configuration
Many parts of the code now use a configuration-to-beans
transformation which allows easy customizations of the many
parts of Magnolia. For example you can reconfigure the
implementation class of the user manager. All properties are
then populated by the configuration (supporting child-beans,
lists, maps). All that is combined with observation and
automates component reloading upon modifications.
We separated the modules and designed them in a way that
multiple security and cache filters can coexist. All filters
can be bypassed which allows implementing sophisticated
custom solutions. As the filters are using the new
configured beans feature, you can for instance implement
complex virtual uri mappings.
We added the concept of URL protection so URLs can now be
protected independently of the website content. We improved
the concept of supporting the anonymous role and context. We
also added the concept of user realms which allowes us to
create a public user registration module (to be released
Easier integration with other frameworks
We removed many obstacles regarding the integration of
Magnolia and other frameworks. For example, the web.xml
file has been drastically simplified, and now contains only
two entries: a filter and a context listener. We also
enabled the support for on-forward filter dispatching. This
allows using another framework that forwards/dispatches to a
Magnolia url. (Whatever you pass as request attribute is
then available in the template). To increase the flexibility
we also added paragraph renderers, allowing special
paragraph implementations. (We now have experimental support
for freemarker-based paragraph rendering and a prototype for
Not only is the multiple subscribers feature now available
in the CE edition, we also added support for a more flexible
from/to mapping of activation. The structure of the content
in the subscriber does not need to be a mirror of the
authoring environment anymore.
This is actually not our merit but Magnolia 3.5 is delivered
with jackrabbit 1.3, which is much more stable, flexible and
faster than the version delivered with Magnolia 3.0.
Magnolia is a leading commercial open-source Enterprise Content Management System based on the Java Content Repository standard (JSR-170). Magnolia is renowned for its outstanding combination of ease-of-use and enterprise architecture. It is used to power the digital communication of anyone from governments to leading FORTUNE 500 enterprises in more than 100 countries on all continents of the world.
A supported Magnolia Enterprise Edition exists, available at http://www.magnolia-cms.com