2009-11-03

BPEL & WF4.0

Har pratat lite med Matt Winkler och tydligen har BPEL försvunnit på vägen, dvs det tooling stöd som utlovades på PDC förra året är inte längre med på banan.

Jag tycker detta är supertrist och hoppas på bättring framöver, vi behöver kunna interagera med de verktyg som finns på marknaden och inte behöva börja processen i Visual Studio.

Ett lyckat exempel är Visio toolingen som finns för workflows i SP2010, det är mer sådant jag vill se och då är BPEL en bra plattform eftersom verktyg som exempelvis Enterprise Architect redan har stödet.

Eller har jag fel i att följande låter som något som går att uppnå med WF&WCF

BPEL Design Goals
There were ten original design goals associated with BPEL:

*Define business processes that interact with external entities through Web Service operations defined using WSDL 1.1, and that manifest themselves as Web services defined using WSDL 1.1. The interactions are “abstract” in the sense that the dependence is on portType definitions, not on port definitions.

*Define business processes using an XML-based language. Do not define a graphical representation of processes or provide any particular design methodology for processes.

*Define a set of Web service orchestration concepts that are meant to be used by both the external (abstract) and internal (executable) views of a business process. Such a business process defines the behavior of a single autonomous entity, typically operating in interaction with other similar peer entities. It is recognized that each usage pattern (i.e. abstract view and executable view) will require a few specialized extensions, but these extensions are to be kept to a minimum and tested against requirements such as import/export and conformance checking that link the two usage patterns.

*Provide both hierarchical and graph-like control regimes, and allow their use to be blended as seamlessly as possible. This should reduce the fragmentation of the process modeling space.

*Provide data manipulation functions for the simple manipulation of data needed to define process data and control flow.

*Support an identification mechanism for process instances that allows the definition of instance identifiers at the application message level. Instance identifiers should be defined by partners and may change.

*Support the implicit creation and termination of process instances as the basic lifecycle mechanism. Advanced lifecycle operations such as "suspend" and "resume" may be added in future releases for enhanced lifecycle management.

*Define a long-running transaction model that is based on proven techniques like compensation actions and scoping to support failure recovery for parts of long-running business processes.

*Use Web Services as the model for process decomposition and assembly.

*Build on Web services standards (approved and proposed) as much as possible in a composable and modular manner.

2 kommentarer:

Anonym sa...

I found this site using [url=http://google.com]google.com[/url] And i want to thank you for your work. You have done really very good site. Great work, great site! Thank you!

Sorry for offtopic

Arash sa...

Det var tråkiga nyheter, hade verkligen sett fram emot BPEL...

:(