6:49 a.m.
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: jPDL 3
Affects Versions: jPDL 3.2.3
Reporter: xiong cf
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
8:30 p.m.
New subject: [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...
]
Ronald van Kuijk commented on JBPM-1463:
----------------------------------------
It's not only that the docs do not contain a reference to it or the schema, it's
also that there are not testcases for the behaviour.
Behaviour should be: although the task-node is configured to create the tasks, individual
task within a node can be conditionally created or not. If the condition element or
attribute resolves to true (element has preference over attribute) it is created,
otherwise it isn't. The value of the element or attribute should contain an EL
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
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
8:32 p.m.
New subject: [JBoss JIRA] Updated: (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...
]
Ronald van Kuijk updated JBPM-1463:
-----------------------------------
Workaround Description: Disable the xsd validation by removing the declaration in the
top of the processdefinition.xml
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
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
1:40 a.m.
New subject: [JBoss JIRA] Updated: (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...
]
Thomas Diesler updated JBPM-1463:
---------------------------------
Fix Version/s: jBPM 3.3.2 GA
(was: jBPM 3.3.1 GA)
Deferred to 3.3.2
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.2 GA
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
2:09 a.m.
New subject: [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
12:07 p.m.
New subject: [JBoss JIRA] Updated: (JBPM-1463) Task condition property is implemented but does not exist in jpdl 3.2 schema
[
https://jira.jboss.org/browse/JBPM-1463?page=com.atlassian.jira.plugin.sy...
]
Alejandro Guizar updated JBPM-1463:
-----------------------------------
Summary: Task condition property is implemented but does not exist in jpdl 3.2 schema
(was: task condition element is not exist jpdl3.2.3 schema, but in code)
Assignee: Alejandro Guizar
This little feature only needs a test case and a trivial jPDL schema addition to see the
light.
Task condition property is implemented but does not exist in jpdl 3.2
schema
----------------------------------------------------------------------------
Key: JBPM-1463
URL: https://jira.jboss.org/browse/JBPM-1463
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 3.2.3
Reporter: xiong cf
Assignee: Alejandro Guizar
Fix For: jBPM 3.2.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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:11 p.m.
New subject: [JBoss JIRA] Updated: (JBPM-1463) Task condition property is implemented but does not exist in jpdl 3.2 schema
[
https://issues.jboss.org/browse/JBPM-1463?page=com.atlassian.jira.plugin....
]
Alejandro Guizar updated JBPM-1463:
-----------------------------------
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Issue Type: Feature Request (was: Bug)
Task condition property is implemented but does not exist in jpdl 3.2
schema
----------------------------------------------------------------------------
Key: JBPM-1463
URL: https://issues.jboss.org/browse/JBPM-1463
Project: jBPM
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 3.2.3
Reporter: xiong cf
Assignee: Alejandro Guizar
Fix For: jBPM 3.2.x
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:23 p.m.
New subject: [JBoss JIRA] Updated: (JBPM-1463) Task condition property is implemented but does not exist in jpdl 3.2 schema
[
https://issues.jboss.org/browse/JBPM-1463?page=com.atlassian.jira.plugin....
]
Alejandro Guizar updated JBPM-1463:
-----------------------------------
Priority: Minor (was: Major)
Task condition property is implemented but does not exist in jpdl 3.2
schema
----------------------------------------------------------------------------
Key: JBPM-1463
URL: https://issues.jboss.org/browse/JBPM-1463
Project: jBPM
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 3.2.3
Reporter: xiong cf
Assignee: Alejandro Guizar
Priority: Minor
Fix For: jBPM 3.2.x
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5125
days inactive
5979
days old
7 comments
5 participants
participants (5)
-
Alejandro Guizar (JIRA) -
Ronald van Kuijk (JIRA)
-
Thomas Diesler (JIRA)
-
Tom Baeyens (JIRA)
-
xiong cf (JIRA)