[jboss-jira] [JBoss JIRA] Closed: (JBPM-426) enable jpdl schema extension via namespaces
[ http://jira.jboss.com/jira/browse/JBPM-426?page=all ]
Tom Baeyens closed JBPM-426.
----------------------------
Fix Version/s: (was: jBPM jPDL 3.2.2)
Resolution: Won't Fix
going forward, we want to move to validation as part of scanning the dom tree, not with
xsd schema. it can provide some hints, but it can't do full validation. e.g. with
schema, you can't validate transition destination resolution in the presence of super
states. the conclusion is that fixing the xsd to support multiple namespaces is going to
take us too much time.
when we would see namespace support as our strategic way forward, this would have to be
baked into all the tooling that we provide. if we would update the schema with namespace
support as you refer to, this would be a big task for us. and the end result is that we
still would have to do our own validation while parsing the dom tree.
so therefor we opt for moving towards full validation in the process parsing. and not
depending too much on the schema validation.
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 jPDL 3.2, jBPM 3.1
Reporter: Martin Dirichs
Assigned To: Ronald van Kuijk
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira