[MGNLGROOVY-114] CLONE - ClassNotFoundException when trying to use a Groovy class in config tree Created: 28/Mar/14  Updated: 07/Jan/16  Resolved: 07/Jan/16

Status: Closed
Project: Magnolia Groovy Module
Component/s: integration
Affects Version/s: 2.3
Fix Version/s: None

Type: Bug Priority: Critical
Reporter: Federico Grilli Assignee: Federico Grilli
Resolution: Outdated Votes: 0
Labels: regression
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
clones MGNLGROOVY-113 ClassNotFoundException when trying to... Closed
dependency
depends upon MAGNOLIA-5726 Use IoC to set a custom ClassFactory Open
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

 Description   

The issue was reported by Teresa. See also attached screenshots. Trying to swap a Java class with a Groovy one throws a CNFE. The reason is that, started from version 2.2 GroovyClassFactory is no longer replacing the DefaultClassFactory due to a misconfiguration in the module descriptor. Here we can use our IoC component declaration mechanism, once MAGNOLIA-5726 is fixed.



 Comments   
Comment by Federico Grilli [ 17/Jun/14 ]

For the time being, the issue is solved by MGNLGROOVY-113 and the old properties mechanism

Generated at Mon Feb 12 05:55:43 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.