WorkFlow updates: local class incompatible: stream classdesc serialVersionUID

[Alex Shubert]

Hello,

it seems that I am missing the crucial piece: how to update. It's obvious that class deserialisation requires some sort of additional steps when workflow was changed and in some cases new WF version is incompatible with previous one. 

So, what is correct way to deploy new workflow version? 

Thank you.

-- 

Alex

[Michael Austermann]

Hi Alex,

have you checked these docs?

http://copper-engine.org/docs/content/COPPER-best-practices_1.0.1-en.pdf

http://copper-engine.org/docs/content/COPPER-WorkflowCompatibilityRules-1.1.0-en.pdf

I mostly use the WorkflowDescription annotation and create a new workflow class for every new workflow version, e.g. FooWorkflow_1_0_0, FooWorkflow_1_0_1, FooWorkflow_1_1_0, ...

Workflow instances I always start using their alias.

Also I set the SerialversionUID of the workflow classes, so that downward compatible changes are possible if needed.

/Michael

---

Von: "Alex Shubert" <alex.s...@gmail.com>
An: "COPPER Engine" <copper...@googlegroups.com>
Gesendet: Dienstag, 22. November 2016 14:00:59
Betreff: [COPPER Users] WorkFlow updates: local class incompatible: stream classdesc serialVersionUID

--
You received this message because you are subscribed to the Google Groups "COPPER Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email to copper-engin...@googlegroups.com.
To post to this group, send email to copper...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/copper-engine/9273b802-ae20-43ac-b59f-60a768e7dfe6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Alex Shubert]

Hi, 

sorry for a late answer. No, I didn't read them and going to do it now. 

thank you.