org.drools.ide plugin MANIFEST.MF should be allowed to find classes from other plugins at runtime to correclty resolve facts ---------------------------------------------------------------------------------------------------------------------------- Key: JBRULES-765 URL: http://jira.jboss.com/jira/browse/JBRULES-765 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Eclipse IDE Affects Versions: 3.0.5 Environment: Eclipse 3.2.2 + EMF 2.1 + JBRules 3.0.5 Reporter: Christophe Avare Assigned To: Mark Proctor Priority: Trivial When using Eclipse, each plugin have a limited class loading capability. When used in an Eclipse application (RCP or not), the model and facts usually comes from other plugins, but the packages and rules are scoped by the org.drools.ide plugin class loader. While adding this plugin as a runtime dependency of the other plugins solves the build time problem of creating a package and compiling it, at runtime when rules are fired, the org.drools.ide package cannot resolve the actual class of the facts, raising a ClassNotFoundException. Solving this issue is easy as it involves only an additional line in the plugin MANIFEST.MF: Eclipse-BuddyPolicy: registered Each plugin that wants to expose its classes to the rule engine thus have to have its own exported packages registered with the org.drools.ide by adding: Eclipse-RegisterBuddy: org.drools.ide In their own plugin manifest. This article in eclipsezone have the whole picture: http://www.eclipsezone.com/articles/eclipse-vms/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira