Windows Workflow Foundation 是否符合 WfMC 标准？
Windows Workflow Foundation 是否符合 WfMC 标准？
Is Windows Workflow Foundation compliance with WfMC Standard?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
您正在混合不同的概念，因此您的问题没有意义。
XPDL 与 BPEL、BPMN 等标准一样，只不过是为了通过文本（通常是 XML）或使用图表以图形方式表示工作流而开发的符号。
话虽如此，WF4 是一个低于标准的 .NET API，允许您实现任何选定的标准，例如 WfMC 标准：XPDL。
与 WF3 相比，WF4 是一个高度灵活和可扩展的 API，至少在理论上，它使您可以自由地使用或多或少的代码来实现您可以想象的每种类型的工作流程，具体取决于您想要实现的任务，以及支持从人工工作流程到各种场景（这是 WF4 非常好的案例场景，因为对于可能需要数天、数周甚至数月的工作流程，其持久性实现对开发人员来说几乎是透明的）以系统为中心工作流（例如可以称为 Web 服务的小型工作流）。工作流程监控等服务也很容易实现。
所有这一切都通过工作流设计器实现，该设计器在 VS-2010 中本地实现，并且可以像任何其他 UI 控件一样在任何 .NET 应用程序上重新托管，并且自动将所述工作流转换为 XAML。
我希望您已经意识到这两个概念的区别，因为当 WF4 只是一个 API 时，您不能真正期望 WF4 遵循任何工作流定义标准。
You are mixing different concepts and so your question doesn't make sense.
XPDL, just like BPEL, BPMN, among other standards, are no more than notations developed to represent workflows through text (usually XML) or graphically, using diagrams.
That being said, WF4 is an .NET API which sits below standards, allowing you to implement any chosen standard, such as WfMC Standard: XPDL.
WF4, also in comparison with WF3, is a highly flexible and extensible API which gives you the freedom, at least in theory, to implement every type of workflows you can imagine with more or less code, depending on the task you want to achieve, and supporting scenarios ranging from human workflow (this is a case-scenario where WF4 is really good, because with workflows that can take days, weeks or even months, its persistence implementation is almost transparent to the developer) to system centric workflows (for example small workflows that can be called as WebServices). Services like workflow monitoring are also easily implemented.
All this with a workflow designer which is implemented natively within VS-2010 and that can be rehosted on any .NET application just like any other UI-Control and which translates said workflows to XAML automatically.
I hope you have perceived the difference of the two concepts because you can't really expect WF4 to follow any Workflow Definition Standard when it is just an API.