[
https://jira.jboss.org/jira/browse/JBPM-2560?page=com.atlassian.jira.plug...
]
Alejandro Guizar reassigned JBPM-2560:
--------------------------------------
Assignee: Tom Baeyens (was: Alejandro Guizar)
Elements having a description in the schema that is either not parsed, not exposed in the
API, or both.
1. swimlane description is parsed but not exposed in the API.
2. transition and timer have description elements intermixed with event listeners; the
descriptions are not parsed.
3. wireObjectType, javaType, scriptType, qlType and mailType have descriptions intermixed
with content; again, the descriptions are not parsed.
Tom, any input on what to do with these? To me, only (1) should be acted upon, in (2) and
(3) the description only appears to serve documentation purposes.
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