Virgo OSGi with custom Vaadin component IncompatibleClassChangeError [message #1148100] |
Mon, 21 October 2013 09:01 |
Csaba Pocsai Messages: 1 Registered: October 2013 |
Junior Member |
|
|
Hello everybody,
I keep getting an IncompatibleClassChangeError in the following scenario, and I'm not entirely sure why. Let's say we have the following two bundles deployed in Virgo:
webapp.war
|
+ bin
| |
| + (web application UI code)
|
+ lib
|
+ vaadin.jar
extension.jar
|
+ bin
| |
| + AdditionalUIComponent.class
|
+ lib
|
+ vaadin.jar
The webapp.war bundle is a web application based on Vaadin, which works fine on its own in Virgo. However, I'm trying to contribute a new UI component to the web application from extension.jar. In order to make AdditionalUIComponent compile, I need to add the Vaadin JARs to the extension.jar bundle as well. Unfortunately, due to some outstanding bugs in Vaadin I can't simply deploy the Vaadin JARs as separate bundles, so the only option seems to be to include them in each bundle.
I can instantiate AdditionalUIComponent in the webapp.war code, but as soon as I'm trying to add it to a parent UI component, I get an IncompatibleClassChangeError. The Vaadin JAR versions are the same everywhere, so that can't be the problem. My guess is that the problem is related to having Vaadin objects coming from two different classloaders. Do you have a suggestion for getting around this problem?
Thanks,
Csaba
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04822 seconds