Page History

...

The 5.6 branch brings the Publishing module pack (see  publishing on Git), which is intended to replace the Activation module ( /modules/activation ) and the Transactional Activation module ( /modules/exchange-transactional ). Besides giving a more logical ordering to the publishing functions in Magnolia, the new module pack also sets all workspaces as publishable by default. For an overview and comparison please see Publishing and activation.

 The publishing and activation modules cannot be used side-by-side in Magnolia.

Upgrading to publishing

If you used activation before the upgrade and wish to use  If you wish you may still continue using the original Activation modules in the 5.6 branch, but opting for the new publishing module pack means that , you have to:

• Remove both the activation modules.
• Add all modules from the magnolia-publishing-parent to your bundle, either manually as pre-built jars or as dependencies.
• Check that after the upgrade the subscribers were correctly migrated from /server/activation to /modules/publishing-core/config/receivers .
• Rewrite  Rewrite your custom activation commands to be compatible with the modules of the new publishing module pack.

Please note that the publishing and activation modules cannot be used side-by-side. Use either only Activation or only Publishing. For further information about configuring the new publishing-core module see the Publishing module page.  

Continue using activation

Using activation in the 5.6 branch is still possible, but only after replacing the bundled Publishing moduleand Publishing Transactional modules with the Activation module and the Transactional Activation module, respectively. You can do this in two ways:

• Remove all the publishing JARs from the ../WEB-INF/lib folders of your author and public instances. Add the activation JAR files in their place.
• Exclude the publishing dependencies from the POM and add the old activation dependencies.

page.  See also Publishing and activation.

...