Uploaded image for project: 'jBPM'
  1. jBPM
  2. JBPM-2554

jPDL schema does not contain an attribute "description" for the element task

XMLWordPrintable

    • Compatibility/Configuration
    • Workaround Exists
    • Hide

      Of course you can just use the description-attribute since deployment and parsing still works then but it is very uncomfortable in the GPD or if you want to validate process definitions against the schema.

      Attention: Parsing of process definitions works but the description is not read.

      Show
      Of course you can just use the description-attribute since deployment and parsing still works then but it is very uncomfortable in the GPD or if you want to validate process definitions against the schema. Attention: Parsing of process definitions works but the description is not read.

      The jPDL schema defintion does not contain an attribute named description for the element task. It was just left out. You find a changed schema file attached. Should description be an attribute anyway but rather an element in task? Might be more comfortable with bigger descriptions when hand-editing process definitions. I have no clue how exactly the parsing of the file is done in the engine so I do not know if this would be a major change. For now it would be great to account for the attribute "description" and get this change into the 4.2 release.

      The attribute is not only missing in the schema but it was also forgotten when the parsing of a process definition is done. So the member "description" of a task-object is always null.

              tom.baeyens Tom Baeyens (Inactive)
              sebastian.s Sebastian Schneider (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: