Schema validation problem with JpdlXmlReader.readProcessDefi

[armorris007]

Can anyone help explain why this is happening:

I have a process-definition XML file (validated using a 3rd party XML editor against the published XSD - http://jbpm.org/xsd/jpdl-3.0.xsd) which continues to fail during deployment:

[deploypar] org.jbpm.jpdl.JpdlException: [[ERROR] process definition line 13: cvc-complex-type.3.2.2
: Attribute 'end-tasks' is not allowed to appear in element 'task-node'.]
[deploypar] at org.jbpm.jpdl.xml.JpdlXmlReader.readProcessDefinition(JpdlXmlReader.java:119)
[deploypar] at org.jbpm.jpdl.par.JpdlArchiveParser.readFromArchive(JpdlArchiveParser.java:27)
[deploypar] at org.jbpm.jpdl.par.ProcessArchive.parseProcessDefinition(ProcessArchive.java:46)
[deploypar] at org.jbpm.graph.def.ProcessDefinition.parseParZipInputStream(ProcessDefinition.jav
a:154)
[deploypar] at org.jbpm.jpdl.par.ProcessArchiveDeployer.deployZipInputStream(ProcessArchiveDeplo
yer.java:46)
[deploypar] at org.jbpm.ant.DeployParTask.deploy(DeployParTask.java:69)
[deploypar] at org.jbpm.ant.DeployParTask.execute(DeployParTask.java:57)
[deploypar] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
[deploypar] at org.apache.tools.ant.Task.perform(Task.java:364)
[deploypar] at org.apache.tools.ant.Target.execute(Target.java:341)
[deploypar] at org.apache.tools.ant.Target.performTasks(Target.java:369)
[deploypar] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
[deploypar] at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
[deploypar] at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:4
0)
[deploypar] at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
[deploypar] at org.apache.tools.ant.Main.runBuild(Main.java:668)
[deploypar] at org.apache.tools.ant.Main.startAnt(Main.java:187)
[deploypar] at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)
[deploypar] at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)

The line it complains about is the task-node element below:

<?xml version="1.0" encoding="UTF-8"?>

<process-definition
xmlns="http://jbpm.org/3/jpdl" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://jbpm.org/3/jpdl http://jbpm.org/xsd/jpdl-3.0.xsd"
name="USER_KI_SHELF_LIFE">

...........

<task-node name="createrevalidationtask" signal="unsynchronized" create-tasks="false" end-tasks="true">

specifically it's the "end-tasks" attribute which it states is not allowed. If I remove this, the process-definition deploys correctly. If I try to use it, it fails during runtime validation as above. I can however see this as a valid attribute in the nominated Schema definition?

I'm using JBpm 3.0.2.

Anyone any thoughts?

Cheers,

Andy

[ummadiravi78]

I have tested the same. It works fine for me with jbpm-3.0.2. No complaits about end-tasks attribute. Here is the code I tested.


import org.jbpm.graph.def.ProcessDefinition;
public class ProcessdefTest {

public static void main(String args[]) {
String procdef = "<?xml version='1.0' encoding='UTF-8'?>"+
"<process-definition name='test'>"+
"<start-state name='start' />" +
"<task-node name='createrevalidationtask' signal='unsynchronized' create-tasks='false' end-tasks='true'/>"+
"<end-state name='done' />" +
"</process-definition>";
ProcessDefinition processDefinition = ProcessDefinition.parseXmlString(procdef);
System.out.println("Done");
}

}

May be you want to check the version of the jbpm.jar taken by the classpath.

Ravi Prakash

[armorris007]

Hi Ravi,

Thanks for your response, however, your test case doesn't include the embedded schema definition, against which the validation seems to be failing:

E.g. (see the schema attributes in the process-definition node below)

String procdef = "<?xml version='1.0' encoding='UTF-8'?>"+
"<process-definition xmlns=\"http://jbpm.org/3/jpdl\" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"" +
" xsi:schemaLocation=\"http://jbpm.org/3/jpdl http://jbpm.org/xsd/jpdl-3.0.xsd\" "+
"name='test'>"+
"<start-state name='start' />" +
"<task-node name='createrevalidationtask' signal='unsynchronized' create-tasks='false' end-tasks='true'/>"+
"<end-state name='done' />" +
"</process-definition>";
ProcessDefinition processDefinition = ProcessDefinition.parseXmlString(procdef);

Using the above example you will get the following exception:

org.jbpm.jpdl.JpdlException: [[ERROR] process definition line 1: cvc-complex-type.3.2.2: Attribute 'end-tasks' is not allowed to appear in element 'task-node'.]
org.jbpm.jpdl.xml.JpdlXmlReader.readProcessDefinition(JpdlXmlReader.java:119)
org.jbpm.graph.def.ProcessDefinition.parseXmlString(ProcessDefinition.java:120)

Cheers,

Andy

[armorris007]

Looking at this JIRA issue:
http://jira.jboss.com/jira/browse/JBPM-421

Does this mean the 'end-tasks' functionality was only introduced in 3.1 yet the 3.0.xsd schema incorrectly includes this as a valid attribute of a task node?

Andy

[aguizar]

You are right. The end-tasks feature belongs to the branch 3.1. The 3.0.2 release included a schema which (correctly) did not define that attribute. When the feature was implemented the published schema for v3.0 was updated, and it (incorrectly) defines that attribute.

Could you open a new JIRA issue, linked to 421, to track this confusion?

[armorris007]

Thanks for the clarification.

JIRA issue duly created:
http://jira.jboss.com/jira/browse/JBPM-517

Cheers.