hardcoded keys for standard instances map in class ProcessInstance ------------------------------------------------------------------ Key: JBPM-1245 URL: http://jira.jboss.com/jira/browse/JBPM-1245 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Engine Affects Versions: jBPM jPDL 3.2.2 Reporter: Hauke Rabe in case you replace the "resource.default.modules" to define different definition classes, such as #org.jbpm.taskmgmt.def.TaskMgmtDefinition .........jbpm.taskmgmt.def.ExtendedTaskMgmtDefinition (extends TaskMgmtDefinition) over these definitions new ModuleInstance are created, for example you replace the TaskMgmtInstance with ExtendedTaskMgmtInstance (extends TaskMgmtInstance) ModuleInstance instance = definition.createInstance(); ProcessInstance#addInstance(final ModuleInstance moduleInstance) uses the classname as instance map key, but for example the accessor ProcessInstance#getTaskMgmtInstance() uses hardcoded TaskMgmtInstance.class as key. conclusion: the defined ExtendedTaskMgmtInstance instance must use the TaskMgmtInstance.class as key. -- 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