2 Replies Latest reply on Nov 4, 2005 7:03 AM by tom.baeyens

    jpdl-3.0.xsd and processContents=

    azzazzel

      I went through forums and JIRA but couldn't find any info on this issue (except this one http://jira.jboss.com/jira/browse/JBPM-203).

      According to jBPM 3.0 documentation the content of elements "action", "controller", "variable", "handler" and "assignment" can be used as configuration information of reusable delegation classes as described in 13.2.3. Configuration of delegations.

      However in XML Schema available at "http://docs.jboss.org/jbpm/xsd/jpdl-3.0.xsd" only the "action" element is defined as

      <xs:any processContents="lax" minOccurs="0" maxOccurs="unbounded"/>

      while others miss the processContent attribute
      <xs:any minOccurs="0" maxOccurs="unbounded">

      which means that for any item inside "handler" and "assignment" elements :
      There must be a global declaration for the item available, and it must be schema-valid with respect to that definition.


      Is this a bug or it has some special sense?

      Assuming schema is going to be fixed, what is more likely, making the "action" element stricter or adding processContents="lax" where it is missing ?