[
https://jira.jboss.org/jira/browse/JBPM-2166?page=com.atlassian.jira.plug...
]
Ronald van Kuijk commented on JBPM-2166:
----------------------------------------
Sure someone can add their own binding, but at this point, it breaks
the graphical editor (at this time).
Then that should be fixed (Vote for the issue everyone...)
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.
95% of the time this is ok... And as mentioned, the Task is mostly the only one with
possible, usable extensions and there has been some thought on it... see my response in
the forum as well... Much more clean/visible/.... Lets eat our own dogfood...
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.
Sure, I never said it could not be done like this. The matter of fact is that people start
using things in so many undesired ways, that results in so many blurry problems, questions
etc.. jbpm already uses an interceptor model internally, which is even extensible I think.
We should just not start using this on the process level as well..
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