[#MAGNOLIA-1980] update: update fails with a ConstraintViolationException if workflows are in progress

Magnolia

update: update fails with a ConstraintViolationException if workflows are in progress

Created: 21/Dec/07 11:11 AM Updated: 17/Mar/09 07:48 PM

Component/s:

None

Affects Version/s:

3.5.2

Fix Version/s:

3.5.3

Time Tracking:

Not Specified

File Attachments:

custom_nodetypes.xml (7 kB)

Labels:
Resolution Date:	10/Jan/08 04:07 PM
Date of First Response:	21/Dec/07 11:13 AM

Description

« Hide

Could not perform installation: javax.jcr.nodetype.ConstraintViolationException: /owfe/activation/1196324976061.0/0.1.0__loop: mandatory child node {}MetaData does not exist
at org.apache.jackrabbit.core.ItemImpl.validateTransientItems(ItemImpl.j
ava:549)

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Philipp Bracher [old account - now Philipp Bärfuss] added a comment - 21/Dec/07 11:13 AM

To fix that you have to replace the file repositories/magnolia/repository/nodetypes/custom_nodetypes.xml before you start updating with the one of 3.5

[ Permlink | « Hide ]

Philipp Bracher [old account - now Philipp Bärfuss] added a comment - 21/Dec/07 11:14 AM

You can use the attached file

[ Permlink | « Hide ]

Vivian Steller added a comment - 10/Jan/08 04:07 PM

this only happens when updating from a version pre-3.0.2 (maybe transiently, if you updated 3.0.1 > (ok) > 3.0.2 > (crash) > 3.5).

some more detailed explanation: 3.0.1 had a nodetype definition of the expression node in place that sais "metaData is mandatory" (see owfe-nodetypes.xml in workflow module). This nodetype definition is copied to the repositories/magnolia/repository/nodetypes/custom_nodetypes.xml file when installing 3.0.1. When updating this instance to 3.5 (by either replacing jars or copying the repository to a newly created instance) an update task of 3.5 removes the metadata node. Since you then still have the original custom_nodetypes.xml file in place Jackrabbit complains with the exception above.

As mentioned before, fix this by adjusting the appropriate expression nodetype in custom_nodetypes.xml or just replace the whole file with the one attached entirely.