Tapestry for Nonbelievers
A new article by I. Drobiazko and R. Zubairov introduces v. 5 of the Apache Tapestry component-oriented web framework. The tutorial shows how to create a component and covers IoC in Tapestry and Ajax.
Presentation
Good News: We have re-worked our video infrastructure to provide more reliable service. Please email bugs at infoq.com with any problems.
Recorded at:
Conversations between loosely coupled services
Posted by Gregor Hohpe on Aug 08, 2007 05:11 AM
Summary
In this presentation, Google architect Gregor Hohpe introduces various concepts for to manage more complex interactions between services, including conversations, choreography, and orchestration. He provides a down-to-earth look at these concepts along with the associated Web services standards like WS-BPEL and WS-CDL, and identifies common patterns in service conversation.
Bio
Gregor Hohpe is a software architect at Google, author of "Enterprise Integration Patterns" and a frequent speaker at conferences around the world.
About the conference
JAOO is the premier European developer conference on software technology, methods and best practices. The conference presents in-depth presentations and tutorials by researchers, engineers and trend-setters in software engineering and technology.
In this presentation, Google architect Gregor Hohpe introduces various concepts for to manage more complex interactions between services, including conversations, choreography, and orchestration. He provides a down-to-earth look at these concepts along with the associated Web services standards like WS-BPEL and WS-CDL, and identifies common patterns in service conversation.
Bio
Gregor Hohpe is a software architect at Google, author of "Enterprise Integration Patterns" and a frequent speaker at conferences around the world.
About the conference
JAOO is the premier European developer conference on software technology, methods and best practices. The conference presents in-depth presentations and tutorials by researchers, engineers and trend-setters in software engineering and technology.
RelatedVendorContent
IBM Web 2.0 Developer eKit: Free Tutorials, Webcasts, Whitepapers
Introducing the SpringSource Application Platform
IBM software architect eKit: Grady Booch podcast, whitepapers, articles
Evaluation Guide: Is Your SCM Tool Ready for Agile?
Introducing Project Zero: Building RESTful services for your Web application
WS-BPEL and WS-CDL should live together
by
Paulo Michels
Posted
Aug 10, 2007 6:31 PM
Re: WS-BPEL and WS-CDL should live together
by
Steve Ross-Talbot
Posted
Sep 1, 2007 9:08 AM
Is it possible to download this Presentation?
by
eisen hower
Posted
Aug 12, 2007 9:18 AM
-
I think WS-BPEL and WS-CDL can and should live together, each one giving its best. As Hohpe said, WS-BPEL is intended for process execution, but focus just on one side of the conversation and in my opinion that difficults modeling large and loosely coupled systems. WS-CDL can help on modeling those system by giving a whole view of the conversations and allowing the automatic generation of the endpoints, even BPEL as described by Hohpe. In my opinion WS-CDL is not yet enough mature and its xml syntax is not easily readable. For professional use we must get the help of tools like Pi4SOA. Nice presentation!
-
Hi Floyd! The presentation system DOSE NOT works smoothly in my laptop with my ASL about 2M brandwidth. Is it possible to let us to watch InfoQ's presentation in off-portal style?
-
I agree completely. I would add three things specifically: 1. The pi4soa tool suite from Pi4Tech is now pretty robust and much easier to use. It is open source so try it out. 2. We have provided BPEL generation from WS-CDL for well over 1 year. Oddly enough few people seem to really want it, rather they generate Java directly or use UML generation. 3. BPEL is not the only end point executable language but it is an important one to have under your belt. Gregor has done a great job in explaining what WS-CDL is for. I would say that it provides a standard-based language supported by formalism to ensure correctness and methodology to ensure that it fits in the grand scheme of things and that it is positioned as a means by which architects can describe their SOA in the large and realise the SOA through a number of executable language. All of this with formal type guarantees of correctness.
3 comments
Reply