Community
Participate
Working Groups
Build Identifier: 20110218-0911 I'm using the Email custom task example (Email.wid). It contains a definition of a custom task editor: "eclipse:customEditor" : "org.drools.eclipse.flow.common.editor.editpart.work.EmailCustomEditor" However I cannot open this editor, I tried double-clicking at a work item. Is there any other way to launch the editor or maybe this feature is not implemented yet? Reproducible: Always
This has not been implemented yet; work on this is scheduled to start some time after the first community release with jBPM 5.3 in April.
Partially done. The SampleCustomEditor is used for all Custom Tasks. This allows basic entry of Boolean, Enum, Float, Integer and String data type fields.
Reopened because I'm not sure if a custom dialog is required here. Currently, the I/O Parameters property tab is used to edit work item properties. If this is not enough, or if custom input validation/constraint needs to be done, we should probably add an editor extension to allow display of a custom input dialog.
Scheduled for 1.3.0-M2 (Neon)
Do you know if this will make it into Neon?
I will try to get this in to the June 22 simultaneous release but I don't want to introduce any regressions last minute so I'm not making any promises.
Hi, sorry for bugging you about this. I saw there were a commit on Github but it seemed to be an incomplete one. If we can help with testing or whatnot, please let me know.
Hi Jonas, Adding support for custom editors to the BPMN2 Modeler is a lot more difficult than it seems, not just from a programming point of view but also because of product dependency and licensing issues. The dialog base classes and supporting classes are defined in a Drools library, which are not covered under Eclipse licensing. We would have to either petition the Eclipse Foundation for special consideration of this third party library, or move the jbpm editor extension module under the JBoss/Red Hat umbrella. The recent changes you're referring to are simply prep work to allow the editor to load and instantiate the external Java classes that implement some dialog interface - there really is nothing new to test here. I'm still investigating the legal ramifications of all this. Unfortunately I don't have an estimate of when this will happen.
