[
https://jira.jboss.org/jira/browse/JBPM-2560?page=com.atlassian.jira.plug...
]
Sebastian Schneider commented on JBPM-2560:
-------------------------------------------
Hello Alejandro, hello Tom.
For my part I don't agree fully. I'd like to see them parsed in (2), too. This
could be valueable information at runtime which could be retrieved via the API to use it
in your own application. It would also allow you to use short names for transititions
while having long descriptions available in case you need them.
Task definition does not have some properties set from jPDL task
element
------------------------------------------------------------------------
Key: JBPM-2560
URL:
https://jira.jboss.org/jira/browse/JBPM-2560
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: jBPM 4.1
Environment: jBPM 4.1
Reporter: Phil Bingley
Assignee: Tom Baeyens
Fix For: jBPM 4.4
Attachments: jbpm-api.patch, jbpm-jpdl.patch, JpdlParser.java.patch,
JpdlParser.java.patch, TaskActivity.java.patch, TaskParsingTestCase.java
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
The duedate and priority values in a jPDL task definition are not set on the task
definition when parsed. This means that the due date is not automatically set when the
task is created, nor the priority.
--
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