[MGNLMIGRATION-7] Content2BeanProcessorImpl exceptions when running the migration script from the Groovy Console Created: 12/Mar/12  Updated: 02/Apr/12  Resolved: 28/Mar/12

Status: Closed
Project: Migration 4.4 to 4.5 (closed)
Component/s: None
Affects Version/s: 1.0.1
Fix Version/s: 1.1

Type: Bug Priority: Major
Reporter: Eric Hechinger Assignee: Eric Hechinger
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

CE and EE.


Template:
Acceptance criteria:
Empty

 Description   

When upgrating from 4.4.6 to 4.5 we have the possibility to run the migration script within the upgrade process, or to perform a normal module upgrade (from 4.4.6 to 4.5) and later call the migration script from the Groovy console.
This issue only happens in the second case.

The first step of the migration process is to move and rename nodes (for example: Component templates (former paragraphs) to config:<module name>/templates/components).
In this case, we will face (tons of) WARNings like:

2012-03-12 12:43:42,593 WARN gnolia.content2bean.impl.Content2BeanProcessorImpl: can't resolve class for node /modules/standard-templating-kit/templates/stkArticle
java.lang.ClassNotFoundException: info.magnolia.module.templatingkit.templates.STKTemplate
....

In fact info.magnolia.module.templatingkit.templates.STKTemplate does not exist any more.

IMPORTANT.
Once the migration script ended and Magnolia's restarted, the migrated Magnolia is running fine.



 Comments   
Comment by Eric Hechinger [ 28/Mar/12 ]

To deactivate the node Listener, just set the flag deactivateNodeListener : true in the Configuration.groovy File.

Generated at Mon Feb 12 10:16:17 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.