1 Reply Latest reply on Jul 22, 2005 2:28 PM by kukeltje

    jpdl-3.0.xsd or JbpmXmlReader possible feature missing or er

      Hi, all.
      I have an application that uses jbpm 3.0 and now, I'm trying to load some processdefinition.xml bad written to check how the JbpmXmlReader works in that way.
      In my application some body can load process definitions (par files with a process definition xml file inside).
      The first test I've proven is the next.

      <process-definition named="Prueba Condicional">.........
      ..................</process-definition>

      As you can see, I've changed the attribute "name" of the process-definition element to "named" (what, is obviously wrong), but the JbpmXmlReader works with this change.
      The next code is part of the JbpmXmlReader class:
      // read the process name
       processDefinition.setName(root.attributeValue("name"));

      and with the processdefinition showed earlier, with this code, the name of the processDefinition is set to null.

      On the other hand, in the jpdl-3.0.xsd there's no reference to the "name" attribute in the "process-definition" element.

      What do you think about all of this?

      Thanks.

        • 1. Re: jpdl-3.0.xsd or JbpmXmlReader possible feature missing o
          kukeltje

          That a product is never finished and there is always room for improvement and that is what everybody is working on very hard.

          If you find issues like these and realy think they are a bug or missing feature, please report them in the jira. The best place to keep everything traceable and to get good releasenotes.