[MSHOP-62] Installation of Shop Module on Magnolia 4.5.x throws NoClassDefFoundError Created: 15/Feb/13  Updated: 27/Feb/13  Resolved: 25/Feb/13

Status: Closed
Project: Magnolia Shop (closed)
Component/s: None
Affects Version/s: 1.1
Fix Version/s: 1.1.1

Type: Bug Priority: Neutral
Reporter: Richard Gange Assignee: Teresa Miyar
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Screen Shot 2013-02-15 at 2.29.14 PM.png    
Issue Links:
duplicate
duplicates MSHOP-49 java.lang.NoClassDefFoundError when s... Closed
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   

When installing Shop module on Magnolia 4.5.x a NoClassDefFoundError is thrown. Class not found is info/magnolia/module/templatingkit/util/STKUtil$PrivilegedOperation. This prevents shop's templates from being loaded and cause a "Now install some templates" screen to be shown when trying to view Website (see screen shot).

The workaround at this point is to get the proper magnolia-module-standard-templating-kit-compatibility jar for the version of the standard templating kit that is being used.



 Comments   
Comment by Jan Haderka [ 22/Feb/13 ]

Actually, compatibility module has dependency on other compatibility modules and as such should not be used if not absolutely necessary. Can't you use new templating functions or execute whatever op you are executing in the model in system context instead of introducing this dependency?

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