The whole idea of the pluggable work items is for end users to make it
very easy to create their own node types: simply add a configuration
file that describes the properties of those nodes and register a handler
at runtime to execute it. They even show up in the palette on the
tooling. Check out the documentation on domain-specific work items to
get the details.
If you really want to create a completely new type of node, that is
possible as well (the core is just a pluggable generic process engine),
but then you'll need to dig into the details more, as you need to
specify a lot of information if you want it to support all features: a
node definition class, a node instance class (execution), register an
XML handler and persistence handler, and possibly extend the tooling.
But in 99% of the cases, the pluggable work item approach as described
above should be sufficient.
Kris
Quoting fero <frantisek.kocun(a)gmail.com>:
Kris Verlaenen wrote:
>
>> 3. Is Flow based on its own PVM or jBPM PVM? Is it also possible
to
>> extend flow with new flow constructs?
> It is based on a generic process engine. We offer a set of core
> constructs but this is extensible (for example, to support
OSWorkflow
> migration, a custom node was added to our language to simplify
this
> translation).
>
Thank you Kris!
And is it possible to extend it without changing the drools code
itself.
Something like WorkItemHandler? JBPM is the only I have seen so far,
where
this is possible and I have used it..
--
View this message in context:
http://www.nabble.com/Flow-tp25567961p25613619.html
Sent from the drools - user mailing list archive at
Nabble.com.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
Disclaimer:
http://www.kuleuven.be/cwis/email_disclaimer.htm