Community
Participate
Working Groups
A class loading problem occurs when running a dynamic workflow which contains a generator component written in Xtend. IFileSystemAccess is loaded twice: once by the default class loader, and later by the project class loader, leading to a constraint violation. Caused by: java.lang.LinkageError: loader constraint violation in interface itable initialization: when resolving method "org.eclipse.sphinx.examples.hummingbird20.genfile.DummyGenerator.doGenerate(Lorg/eclipse/emf/ecore/resource/Resource;Lorg/eclipse/xtext/generator/IFileSystemAccess;)V" the class loader (instance of org/eclipse/sphinx/jdt/loaders/ProjectClassLoader) of the current class, org/eclipse/sphinx/examples/hummingbird20/genfile/DummyGenerator, and the class loader (instance of org/eclipse/osgi/internal/loader/EquinoxClassLoader) for interface org/eclipse/xtext/generator/IGenerator have different Class objects for the type ingbird20.genfile.DummyGenerator.doGenerate(Lorg/eclipse/emf/ecore/resource/Resource;Lorg/eclipse/xtext/generator/IFileSystemAccess;)V used in the signature at java.lang.Class.getDeclaredConstructors0(Native Method)
Closed stale issue before migration