[MAGNOLIA-5893] Executing chained Command in Groovy Console fails when (unlicenced?) personalisation module is installed Created: 21/Aug/14  Updated: 30/Aug/16  Resolved: 30/Aug/16

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 5.3.2
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Adi De Masi Assignee: Unassigned
Resolution: Obsolete Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

If you define a chained Command (as described in https://documentation.magnolia-cms.com/display/DOCS/Commands) and execute it in the groovy console, it fails with the following exception:

java.lang.IllegalArgumentException: Invalid indexed property 'Key[type=info.magnolia.personalization.preview.trait.PreviewTraitCollector, annotation=[none]' on bean class 'class com.example.myModule.MyCommand' Invalid index value 'type=info.magnolia.personalization.preview.trait.PreviewTraitCollector, annotation=[none'

Removing the Personalisation-Module solves the problem. It may be related to a missing licence for the Personalisation-Module, because we Use standard, non-pro EE-Version of Magnolia



 Comments   
Comment by Moritz Siuts [ 24/Oct/14 ]

Got the same error on 5.3.4 (EE Edition, but not Professional) with a self defined chained command. Exclusion helps.

Comment by Vincent Gombert [ 23/Feb/16 ]

I've been facing same kind of error with 4.5.3 EE Pro, but not in Groovy Console and not with a personalization module property, mine was Key[type=info.magnolia.cms.core.AggregationState, annotation=[none]].
Nevertheless i solved it using SimpleContext instead of ContextDecorator. As MgnlGroovyConsoleContext extends ContextDecorator, it might be helpful to execute the command with new SimpleContext() instead of ctx. The reason is SimpleContext does not delegate getAttributes to the embedded context so you are not bothered with context attributes you don't even care of.

Comment by Richard Gange [ 30/Aug/16 ]

Since personalization 1.1.2 the feature is now EE std. Compatible with 5.3.3

Generated at Mon Feb 12 04:09:23 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.