The BPEL4People and WS-HumanTask specs are headed to OASIS, resulting in a new BPEL4People Technical Committee (TC) - expect to see an announcement and call for participation soon. The TC will focus on defining human interactions (human tasks) as part of a WS-BPEL process, enabling these definitions to be exposed as web services.
Web Services Interoperability Technology (WSIT) is an open-source implementation of next generation Web services technologies that deliver interoperability between Java EE and .Net to help you build, deploy, and maintain Composite Applications for your Service Oriented Architecture. Built upon JAX-WS (Java API for XML Web Services), this implementation will be made available as the "Web Services Interoperability Technology (WSIT)" and is focused on four main categories: Messaging, Metadata, Security, and Quality-of-Service (QoS).
(Found in a blog, "Versioning is as inevitable as security.") SOA development practice isn't much different from other software development practices except for design and maintenance. Multiple self-containing and aggregated services that interact with others have their own lifecycle and evolution. The loosely coupling model of SOA services significantly simplifies design but creates additional difficulties in maintenance, especially in the interoperability of different service versions
Here you'll get thehands-on knowledge of Web Services security in Java EE that we acquired when adding security support to OptimalJ-generated SOA applications. It's based on the J2EE 1.4 specification itself as well as on what is actually supported and it works in three major J2EE 1.4 application servers - JBoss 4.0.4, WebSphere 6.0.2.x, and WebLogic 9.1. You'll also learn about the new mandatory security features available to Web Service endpoints in Java EE 5.0.
[May 2, 2005] XML and Web Services security specifications define elements to incorporate security tokens within a SOAP message. We propose a method for mapping such messages to an abstract syntax in the style of Dolev-Yao, and in particular Casper notation. We show that this translation preserves flaws and attacks. Therefore we provide a way for all the methods, and specifically Casper and FDR, that have been developed in the last decade by the theoretical community for the analysis of cryptographic protocols to be used for analysing WS-Security protocols. Finally, we demonstrate how this technique can be used to prove properties and discover attacks upon a proposed Microsoft WS-SecureConversation protocol.
May/June 2006. Mobile devices and server applications often run on different platforms, which can make integration problematic. Web services might offer a solution, but they typically include XML protocols that are too â€œheavyâ€ for mobile devices. The authorsâ€™ proposed framework is designed to adapt Web services to mobile environments by using mobile agents to enable the development of high-performance Web service applications.
[June 2006] Summary: This whitepaper provides a high-level overview of Microsoft support for Web services across its product offerings. Microsoft interoperability efforts and involvement in the Web services standardization process are also discussed. (47 printed pages)
Tips for integrating with application service providers using Web services.
Book published by Packt Publishing in June 2006. Ten practical real-world case studies combining business process management and web services orchestration. Real-world BPEL recipes for SOA integration and Composite Application development. Combining business process management and web services orchestration. Authors: Matjaz Juric, Stany Blanvalet, Jeremy Bolie, Michael Cardella, Sean Carey, Praveen Chandran, Yves Coene, Kevin Geminiuc, Arun Poduval, Lawrence Pravin, Jerry Thomas, Doug Todd, The Hoa Nguyen, Markus Zirn, Harish Gaur
Tim Bray's comments on Web Services at a Crossroads by Daryl Plummer
Find out about XForms and why they are the perfect partner for Web Services. By Craig Caulfield, Mar. 6, 2006
Web services have evolved from plain application-integration enablers to value-added stand-alone functionality providers such as getting a quote to a comprehensive business function like processing orders. Enterprises are exploiting this new revenue model by offering such business functions as services on usage basis. Information sharing instances such as Amazon's e-commerce services have helped in the creation of new powerful solutions using business functions as services. By Naveen Kulkarni; Manivannan Gopalan; Geo Philips Kuravakal; Lipika Sahoo; Sunny Saxena, in SOA Web Services Journal, February 27, 2006.
It's tremendously difficult to argue a RESTful approach to a service-oriented architecture (SOA), when the corporate mindshare is SOAP--where project stakeholders tout the SOA buzzword, nod their heads sagely when you say SOAP, nod their heads again when you say XML-RPC, and then look blankly when you mention REST. At an official level, it seems that for the IBMs, Suns, Microsofts, and Oracles (et al) of this world, REST isn't even on the radar; perhaps more because they would find it difficult to build a commercial strategy around something that is based on simplicity and standards (like HTTP) that have been around for years, than from a true lack of visibility at the coalface.
Oxygen is a multi-platform XML Editor, XSLT/XQuery Debugger and Profiler written in Java. It supports XML, XSL, XQUERY, FO, XSD, RNG, RNC,NRL, DTD, Schematron, WSDL and CSS documents. It offers a powerful and intelligent code insight that guides the user to write valid XML content. The code insight can be driven by a DTD, an XML schema, an Relax NG schema or by the structure of a partial edited document. It has FOP and full Unicode support.
The Achilles' heel of service-oriented architectures (SOAs) has been policy enforcement. A standard is emerging for run-time control: the Governance Interoperability Framework (GIF). Web Services Pipeline, 1 June 2005.
Luis Felipe Cabrera, Christopher Kurt and Don Box, Microsoft Corporation, September 2004. This white paper provides an introduction to the Web services architecture. It describes the design principles underlying the architecture and foundational technologies for Web services. Features are described and linked to the specifications that formally define them. This paper also serves as a reference guide to all the specifications in the architecture. (45 printed pages)
Mark Nottingham, 11 August 2004. One of the foundations of most vendors' approach to Web services is called document-oriented messaging. This is the notion that interoperability is improved by describing a protocol in terms of the artefacts that are exchanged on the wire, rather than how the code that handles them is written.
StrikeIron is a provider of intelligent web services applications including the Web Services Business Object layer.
How does the ‘new world’ of Web services fit into ‘old world’ EAI? Very nicely, thank you, provided vendors and users alike keep Web services in perspective, and Web services standards and solutions continue to mature.
Essay by Tim Bray from Sun.
The Patterns for e-business are a group of proven, reusable assets that can be used to increase the speed of developing and deploying Web applications. This redbook focuses how the Self-Service and Extended Enterprise business patterns, and the Application Integration pattern, can be used to start implementing solutions using the service oriented architecture approach.
Indigo is part of "Longhorn," the upcoming version of Windows. I believe that the marketing message is new and is shifting slightly .NET direction from Web Services to Service Oriented Architecture and Service Oriented Programming.
This joint Microsoft and IBM paper provides a succinct overview for the set of Web service specifications that address these needs. For the details of the specifications we provide references to the actual documents. The main purpose of this paper is to briefly define the value these specifications provide to our customers. We also describe how these specifications complement each other to compose robust environments for distributed applications.
Globalization is the proper design and execution of systems, software, services, and procedures so that one instance of software, executing on a single server or end-user machine, can process multilingual data and present culturally correct information (for example, collation, date, and number formats). This article starts from the base elements of a globalization architecture and then applies them to the Web services architecture. To strengthen the ideas, some examples are raised in the paper, together with some references for further information.
Applying Semantics in Annotation, Quality of Service, Discovery, Composition, Execution. The METEOR-S project at the Large Scale Distributed Informaton Systems (LSDIS) Lab at the University of Georgia supports Semantic Web Process management. It investigates broad based use of semantics in the entire Web process lifecycle encompassing semantic description/annotation, discovery, composition and enactment (choreography and orchestration) of Web services. Semantics covered include: input/output (messages), functional, execution, and quality of service.