[
https://jira.jboss.org/browse/JBRULES-2716?page=com.atlassian.jira.plugin...
]
Simon Bronner edited comment on JBRULES-2716 at 10/1/10 2:07 AM:
-----------------------------------------------------------------
Appears to be a bug in org.drools.bpmn2.legacy.beta1.UserTaskHandler (and also present in
org.drools.bpmn2.xml.UserTaskHandler.handleNode). Although a minor bug, it does have
repercussions for logging, debugging, reporting, etc. (If it IS a bug! Perhaps I'm
misunderstanding the meaning of WorkItem.getName() ?)
was (Author: sxb8au):
Appears to be a bug in org.drools.bpmn2.legacy.beta1.UserTaskHandler (and also present
in org.drools.bpmn2.xml.UserTaskHandler.handleNode). Although a minor bug, it does have
repercussions for logging, debugging, reporting, etc.
WorkItem getName always returns "Human Task" when using a
bpmn model schema
---------------------------------------------------------------------------
Key: JBRULES-2716
URL:
https://jira.jboss.org/browse/JBRULES-2716
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-core (flow)
Affects Versions: 5.1.0.FINAL
Environment: java version "1.6.0_21"
Reporter: Simon Bronner
Assignee: Mark Proctor
Priority: Minor
Regardless of the Name defined for a userTask in the bpmn, "Human Task" is
always returned on a call to getName() on org.drools.runtime.process.WorkItem
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira