[
https://jira.jboss.org/jira/browse/JBPM-2166?page=com.atlassian.jira.plug...
]
Gregg Freeman commented on JBPM-2166:
-------------------------------------
Sure someone can add their own binding, but at this point, it breaks the graphical editor
(at this time).
The problem with the custom node is that there is zero thought for reuse of out-of-the box
functionality. If I want to override existing task functionality, the only way to do it
using the "approved" API is to completely rewrite/re-implement the existing Task
behavior.
One can easily do this by inheritance / delegation in custom code, and you get the same
capability with an interceptor model as well. Seems like an easy way to add a _bunch_
more flexibility if people need it.
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