[BLOSSOM-132] ClassNotFoundException when trying to integrate Magnolia 5.1 with Blossom 3.0 Created: 18/Sep/13 Updated: 07/Nov/14 Resolved: 20/Sep/13 |
|
| Status: | Closed |
| Project: | Blossom |
| Component/s: | None |
| Affects Version/s: | 3.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Sigurd Rolfes | Assignee: | Tobias Mattsson |
| Resolution: | Not an issue | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
JBoss eap 6.1 startet in IntelliJ |
||
| Attachments: |
|
| 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 |
|
We are trying to get Blossom 3.0 work with a Magnolia 5.1 Version (CE). A ClassNotFoundException is thrown when starting up JBoss, missing class is: info.magnolia.ui.api.vaadin.WidgetsetDefinition See full stacktrace in the file attached. We cannot find any references in the code and there is no package "vaadin" in the magnolia-ui-api module. Our dependencies: <dependency> <dependency> Further we have: Magnolia-Version 5.1-SNAPSHOT and STK 2.6-SNAPSHOT Seems that there is something missing that has the WidgetsetDefinition class inside. |
| Comments |
| Comment by Sigurd Rolfes [ 18/Sep/13 ] |
|
I found the following Ticket: I've got two admincentral jars, one is 5.1-SNAPSHOT, one is alpha1: magnolia-ui-admincentral-5.1-alpha1.jar In this jar there is an old ui-admincentral.xml in the META-INF directory that contains old configuration entries for typeMapping: <type-mapping> The package "vaadin" does not exist anymore. |
| Comment by Sigurd Rolfes [ 18/Sep/13 ] |
|
Tried to use Blossom 3.0-SNAPSHOT The pom in nexus has an entry for Magnolia version of alpha1 I guess this is the place where the admincentral-alpha1 and other alpha1 jars come from. <magnoliaVersion>5.1-alpha1</magnoliaVersion> |
| Comment by Sigurd Rolfes [ 18/Sep/13 ] |
|
ok, I've got it working. Problem seems to be the wrong alpha1 Version entry in the nexus poms. I got rid of the magnolia-ui-admincentral jar with the typeMapping entries referencing the non-existing WidgetsetDefinition class resp. package "vaadin". Probably the post should be updated, alpha1 may only work with Magnolia core alpha1. http://tobias-mattsson-magnolia.blogspot.de/2013/08/blossom-3-alpha1-released.html |
| Comment by Tobias Mattsson [ 20/Sep/13 ] |
|
Hi Sigurd, Indeed, blossom 3.0 alpha1 is intended to be used with Magnolia 5.1 alpha1. I will update the blog post to make this clear. |
| Comment by Tobias Mattsson [ 20/Sep/13 ] |
|
Also, RC1 was released on tuesday this week. http://tobias-mattsson-magnolia.blogspot.se/2013/09/blossom-30-release-candidate-1-released.html |