This content has been marked as final. Show 1 reply
The schema allows any element to appear as child of the controller element. From jpdl-3.0.xsd:
<xs:element name="controller" minOccurs="0"> <xs:complexType> <xs:sequence> <xs:any minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> <xs:attribute name="class" type="xs:string" use="optional"/> <xs:attribute name="config-type" type="configType" use="optional"/> </xs:complexType> </xs:element>
There is a semantic restriction, tough (as opposed to syntactic). The jBPM manual, sect. 13.3.26 states:
if no task controller handler is specified, the content must be a list of variable elements
This makes sense because you need a new controller (referenced by the class attribute of element controller) that is able to read the custom configuration.