[
https://jira.jboss.org/jira/browse/JBPM-2166?page=com.atlassian.jira.plug...
]
Ronald van Kuijk commented on JBPM-2166:
----------------------------------------
Gregg,
In my humble opinion this makes things to complicated. On the one hand you say the nodeset
(which includes implementation aka behaviour) is sufficient but you want it extensible.
jPDL itself is extensible in a different way. See the jbpm.jpdl.bindings.xml file in the
source. Implementing new activities (and overriding) existing ones is possible that way.
Using additional behaviours (in a way like interceptors?) like you propose is imo not
needed, also because it still is the intention to have the task behaviour be a 'mini
process' in itself (see jbpm.task.lifecycle.xml in the pvm module source). So instead
I would enhance the task behaviour etc with things that are valid usecases. That way
*anyone* can benefit....
This specific issue is therefore not specifically meant to make the workflow, but to add
properties etc to e.g. a task (like avg-duration etc) that you can use when accessing the
task via the api (like task.getProperty('avg-duration') and other things. But I
admit that this is partly my personal interpretation.
add extensibility to jpdl schema
--------------------------------
Key: JBPM-2166
URL:
https://jira.jboss.org/jira/browse/JBPM-2166
Project: jBPM
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Tom Baeyens
Assignee: Tom Baeyens
Priority: Optional
Fix For: jBPM 4.x
Attachments: jpd-example.jpdl.xml
Add activity pluggability. (add the proper any's and anyAttributes)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira