工作流基础从业务对象反序列化
我正在研究 Microsoft WF 示例，发现它们序列化/反序列化未完成的工作流程以保持其状态。我不喜欢它，因为工作流是一个过程，它不需要任何额外的数据来从不同的线程或代码部分继续。
也许我错过了什么。如果可能的话，您能否分享保存/加载未完成工作流程的示例？也许替代工作流框架可以不需要序列化/反序列化。例如，它可以从业务对象状态恢复。
I'm studying Microsoft WF samples and have found that they serializing/deserializing workflows that are not finished to hold its state. I don't like it as workflow is a process and it doesn't need any additional data to continue from a different thread or code part.
Maybe I've missed something. Can you share examples of saving/loading unfinished workflows if it's possible? Maybe alternative workflow frameworks can do without serialization/deserialization. For example it could be restored from business object state.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
你想得太小了。它的用途有很多，超乎你现在的想象。所有工作流框架（除非它们使用某种类型的对象数据库？）都会序列化工作流状态，以便稍后可以继续。 Microsoft WF、K2 BlackPerl 和许多其他公司都这样做。 K2 这样做是因为您可以让一个项目经历工作流程 v1，然后在中间有人会将工作流程更新到 v2，但 K2 足够聪明，知道应该继续在 v1 工作流程下处理该项目。
也许我错过了你的问题，但你似乎不喜欢它序列化存储工作流程。
You're thinking far too small. There are many uses beyond what you can imagine right now. All workflow frameworks (unless they use some type of object db?) will serialize the workflow state so it can be continued at a later time. Microsoft WF, K2 BlackPerl and many others do this. K2 does it because you can have an item going through workflow v1 and then right in the middle someone will update the workflow to v2 but K2 is smart enough to know that is should continue processing that item under the v1 workflow.
Maybe i'm missing your question but it seems like you don't like that it serializes the workflow for storage.