Clone

[msandoz]

This question is related to my earlier one about cut/copy/paste support. Has anyone done any work on cloning nodes etc?

Is this a feature that would be desirable in the base classes that are going to be cloned or is it better to have the clone as a set of external utility methods?

Anyone have any thoughts on how deep to clone?

Anyone have any thoughts on lifecycle/dependencies between the xml adapters, the notational and semantic elements - relating to cloning - so that they stay in sync?

Should the clonings be part of the command structure?

Thanks for any input!

[camunda]

I don't get it, what do you want to clone. Node's of the process definition?

Where, while design time in the designer?

The Command's apply only on stuff done with the jbpmContext, so if you would like to clone a process already deployed, that may be a command...

So, what's the use case for that cloning?

[tom.baeyens]

i think msandoz means copy-and-paste in the designer and not the runtime.

[koen.aers]

Yes, Matthew is one of the hardcore designer extenders ;-)

I would expect that when I clone a node, I clone the whole Monty... But maybe others expect other things.

Regards,
Koen

[msandoz]

quite right Koen, i mean to copy the nodes at design time.
Since this is for cut/copy/paste functionality i will need to copy the action handler and its data, as well as other node attributes. For other types I will have to copy their attributes as well. i will also need to copy included transitions - that is those whose endpoints are both within the selection set.
if i decide to support it for the tree as well, i'll need to also be able to copy things like actions, tasks, etc though that is a secondary concern right now.