BPEL is absolutely inappropriate as the base language for WF.
  1. BPEL is much too complicated.
  2. BPEL works on the assumption that you are invoking services, and that the services already exist -- you don't write the core services in BPEL. WF is a framework that you could use to write the business logic of the core services.
  3. A BPEL processor can be built on a foundation of WF.
WF uses a declarative programming model for expressing business logic. Therefore it needs a declarative programming language -- XAML. (XAML is designed to express business logic as well as UI widgets.)

Here's a good article on WF by Don Box and Dharma Shukla:
http://msdn.microsoft.com/msdnmag/issues/06/01/WindowsWorkflowFoundation/default.aspx

WinFX includes a technology called Windows Workflow Foundation that allows programs to be expressed as declarative, long-running processes called workflows. Unlike traditional Microsoft® .NET Framework programs, workflow-based programs are typically specified in a declarative Extensible Application Markup Language (XAML) document that specifies the structure of the program in terms of domain- specific activities. These activities are typically implemented in a traditional common language runtime (CLR)-based programming language such as C# or Visual Basic®.

WinFX provides a set of general-purpose activities that cover most control flow constructs, but users are free to ignore them and write an entirely new set of activities that are precisely tailored to the problem domain they are working in. More commonly, a workflow program will use WinFX-provided activities for basic control flow and program structure, and will use custom user-defined activities for domain-specific functionality.

In addition to supporting a XAML-based compositional approach to creating programs, workflow-based programs also benefit from a richer set of runtime services than traditional CLR-based programs. The WinFX workflow runtime can be hosted in any CLR AppDomain. The runtime allows workflows to be removed from memory (a technique called passivation) and later reloaded and resumed without making developers write explicit state management logic. The workflow runtime also provides common facilities for handling errors and compensating transactions to allow either automatic or customized undo logic to be specified for long-running units of work. In addition, you can take advantage of management services that allow the state of a given workflow program to be inspected either through eventing, tracking, or querying the workflow state.

Anne


On 1/19/06, Ron Schmelzer <[EMAIL PROTECTED]> wrote:
More specifically, WWF is a set of libraries that end-users and ISVs can use when they are building their own business process and workflow systems. However, it's not clear (to me at least) how XAML fits into the mix and how it relates to their usage of BPEL. Anne - have you seen more details on that?

R


Anne Thomas Manes wrote:
The latest version of Windows Workflow Foundation (WinWF) now uses XAML for its worflow markup format. I'm not sure that quite qualifies as using "XAML for business process", because WinWF is not really a business process system. It's a low-level framework for building workflow applications. It supports human, system, and state-based workflow. The next rev of BizTalk will build on WinWF. Office 12 will also provide a set of built-in workflw capabilities (e.g., for routing documents for approval) based on WinWF.

Anne

On 1/18/06, jeffrschneider <[EMAIL PROTECTED] > wrote:
"They are really pushing the use of XAML for business process, which
is very unique and compelling," said Ron Schmelzer, a senior analyst
with ZapThink LLC. "They're already getting WCF and WF in the
mainstream."
See: http://www.eweek.com/article2/0,1895,1912323,00.asp


Ron - what does XAML for business process mean? Also, why is it
compelling?
Thanks in advance,
Jeff










Yahoo! Groups Links

<*> To visit your group on the web, go to:
     http://groups.yahoo.com/group/service-orientated-architecture/

<*> To unsubscribe from this group, send an email to:
    [EMAIL PROTECTED]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/





-- 
_____________________________________________________________
Ronald Schmelzer
[EMAIL PROTECTED]
Senior Analyst
ZapThink LLC
Direct: 781-577-2779 / Main: 781-207-0203


    


  

SPONSORED LINKS
Service-oriented architecture Computer monitoring software Free computer monitoring software


YAHOO! GROUPS LINKS






SPONSORED LINKS
Service-oriented architecture Computer monitoring software Free computer monitoring software


YAHOO! GROUPS LINKS




Reply via email to