[
https://jira.jboss.org/jira/browse/JBPM-1244?page=com.atlassian.jira.plug...
]
Tom Baeyens commented on JBPM-1244:
-----------------------------------
this limitation should be documented in the documentation. fixing will take too much
time. jbpm 4 will improve this extension mechanism anyway.
hardcoded keys for standard definitions map in class
ProcessDefinition
----------------------------------------------------------------------
Key: JBPM-1244
URL:
https://jira.jboss.org/jira/browse/JBPM-1244
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Core Engine
Affects Versions: jBPM 3.2.2
Reporter: Hauke Rabe
Assignee: Thomas Diesler
Fix For: jBPM 3.3.2 GA
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)
ProcessDefinition#addDefinition(final ModuleDefinition moduleDefinition) uses the
classname as definition map key, but for example the accessor
ProcessDefinition#getTaskMgmtDefinition() uses hardcoded TaskMgmtDefinition.class as key.
conclusion: the defined ExtendedTaskMgmtDefinition instance must use the
TaskMgmtDefinition.class as key.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira