enable jpdl schema extension via namespaces ------------------------------------------- Key: JBPM-426 URL: http://jira.jboss.com/jira/browse/JBPM-426 Project: JBoss jBPM Issue Type: Feature Request Components: Core Engine Affects Versions: jBPM 3.1, jBPM jPDL 3.2 Reporter: Martin Dirichs Assigned To: Ronald van Kuijk Fix For: jBPM 3.3 Customizing jpdl elements in a process definition via application-specific XML-elements is currently only possible outside of any schema validation. XML namespaces are the canonical way to allow for the extension of jpdl so that configuration data of delegation classes may be defined within an application-specific namespace and associated XML schema. In particular, this would be necessary to enable customization of jpdl elements - action - assignment - handler - controller - task Bug #JBPM-332: http://jira.jboss.com/jira/browse/JBPM-332 is somewhat related to this issue. However, resolution of JBPM-332 - only allows for arbitrary elements to appear inside jpdl files (without schema validation) - and only for customizing assignments (leaving out action, handler, controller and task). Implementation of this feature request would be done via a more intelligent version of an EntityResolver (defined in org.jbpm.jpdl.xml.SchemaValidationHandle) that can return application specific schemas in addition to the default one for jpdl.