Bits & Notes
Friday, June 02, 2006
VS 2005 Web Application Projects, MSBuild, and Continuous Integrations
Scott Guthrie on Continuous Integrations.
 
ASP.NET 2.0 Localization
Source: Scott Guthrie's Blog

Some resources on the new localization features for ASP.NET 2.0:
 
The Development Abstraction Layer
The Development Abstraction Layer: An excellent piece from Joel Spolsky.
 
Jesus Rodriguez on WWF
The Persistence Service and The Transaction Service
 
BPM Think Tank: BPMN Technology Roundtable
Sandy Kemsley blogs her notes for the BPMN Technology Roundtable of the BPM Think Tank 2006. Two important quotes:

OMG is not recommending XPDL for serialization of BPMN, but recommends the use of BPDM.

[There are] some ideas about defining aspects of a process, such as security, escalation and exception handling, in order to simplify the primary representation. The aspects would be invoked whenever an activity is executed, but represented on separate diagrams. In that way, an aspect would effectively be a template for activities that could be overlaid on any of the activities in the main diagram and extend the meaning of the main diagram. Each activity in the main diagram would need a mechanism for passing some number of parameters to the instance of each aspect that may execute for that activity, for example, some measure of the time-criticality of an activity in order to trigger an escalation at the approriate time.

 
On the differences of BPEL and XPDL
Sources:
Swenson [Fujitsu] came back to the issue of XPDL versus BPEL, which he doesn't see as competing. XPDL is about process design, about serializing and saving what you drew in BPMN, and not so much about execution. He sees XPDL as a way of moving a process from one design/simulation/analysis tool to another (about 30 tools support it today), whereas BPEL is about the nuts and bolts of sending messages from one location/service/system to another. As Evdemon [Microsoft] said, XPDL is like XMI for business processes. Swenson states that XPDL will continue to track and adjust to any changes to BPMN.
 
Is Workflow "Back"? (Did It Ever Go Away?)
Bruce Silver's opinion for the usage of the term "workflow":
So… is workflow “back”? In one way I think it is, with the growing recognition among the orchestration-style vendors that the action today in the BPM market is focused around human work, not application integration. I think that’s what motivated BEA-Fuego, why IBM and SAP are now behind BPEL4People (when they could have done human tasks in BPEL from the start), and why Oracle is putting so much into its human workflow capabilities. So, yeah, workflow is back. But just don’t call it that.
 

Name: Panos
Location: Πειραιάς, Greece
ARCHIVES
June 2006 /


Powered by Blogger