[jbpm-issues] [JBoss JIRA] Commented: (JBPM-1463) task condition element is not exist jpdl3.2.3 schema, but in code
[
https://jira.jboss.org/jira/browse/JBPM-1463?page=com.atlassian.jira.plug...
]
Tom Baeyens commented on JBPM-1463:
-----------------------------------
i never recall adding conditions to tasks. so i'm ok with
1) keeping it as an undocumented feature. it could be added to the schema. but not to
the docs as then we'll have to support it.
2) removing it completely. be carefull not to remove the condition member of the task as
that will change the schema.
since people might be using it, i'm in favour with (1)
i think it is a nice addition, but let's work it out on jbpm 4 only.
task condition element is not exist jpdl3.2.3 schema, but in code
-----------------------------------------------------------------
Key: JBPM-1463
URL: https://jira.jboss.org/jira/browse/JBPM-1463
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Core Engine
Affects Versions: jBPM 3.2.3
Reporter: xiong cf
Fix For: jBPM 3.3.x
in jpdl-3.2.xsd :
<xs:element name="task">
<xs:complexType>
<xs:choice minOccurs="0" maxOccurs="unbounded">
<xs:element ref="description" />
<xs:element ref="assignment"/>
<xs:element ref="controller"/>
<xs:element ref="event"/>
<xs:element ref="timer"/>
<xs:element name="reminder">
<xs:complexType>
<xs:attribute name="duedate" type="xs:string"
use="required" />
<xs:attribute name="repeat" type="xs:string" />
</xs:complexType>
</xs:element>
</xs:choice>
<xs:attribute name="name" type="xs:string" />
<xs:attribute name="blocking" type="booleanType"
default="false"/>
<xs:attribute name="signalling" type="booleanType"
default="true"/>
<xs:attribute name="description" type="xs:string" />
<xs:attribute name="duedate" type="xs:string" />
<xs:attribute name="swimlane" type="xs:string" />
<xs:attribute name="priority" type="priorityType"
default="normal" />
<xs:attribute name="notify" type="booleanType"
default="false"/>
</xs:complexType>
</xs:element>
is not exist element condition.
but in org.jbpm.jpdl.xml.JpdlXmlReader line312 has:
// get the condition
String condition = taskElement.elementTextTrim("condition");
if (condition!=null) {
task.setCondition(condition);
} else {
task.setCondition(taskElement.attributeValue("condition"));
}
and in org.jbpm.graph.node.TaskNode line161 has:
if ( (createTasks)
&& (tasks!=null) ) {
Iterator iter = tasks.iterator();
while (iter.hasNext()) {
Task task = (Task) iter.next();
executionContext.setTask(task);
if (evaluateTaskCondition(task.getCondition(), executionContext)) {
tmi.createTaskInstance(task, executionContext);
}
}
}
I think in jbpm3.2.3 should be spport task condition element , but document and schema
not new
--
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