EMEA Web Services Competency Workshop in Norway
Are you interested in Web Services architecture and technology and coincidentally live in Norway? If yes, the EMEA Web Services Competency Workshop might be exactly what you’re looking for. It takes place on the 1. March in Oslo. This workshop usually last for two days but I “compressed” it into a day full of WS-* related content:
· Update on SOA and the Web Services platform
In short, SOA is about loosely coupled systems, message based communication and business process orchestration. As an abstract architectural model, it acts as an indirection between the business and the technology model. Web Services are the preferred implementation technology for loosely coupled and interoperable systems. We’re going to elaborate the most recent movements in this area and discuss the motivations for the latest WS specifications.
· The grey area between service and object-oriented design
Realizing a service oriented architecture usually implies the usage of object-oriented technologies. There exist different issues if we map service oriented concepts to object oriented implementations. We discuss the challenges of exposing objects as part of a stable service interface, talk about the impact of service autonomy, the definition of a "well formed" contract as well as service versioning. Although it's architecture; expect to see code, XML and WSDL.
· Best practices for Web Services interoperability
If moving towards service oriented architecture, interoperability is one of the key requirements. We’re going to cover Web Services interoperability based on best practices gained on real world projects. Beside some architectural thoughts; we're going to discuss the pro and cons of the different SOAP encodings (rpc-literal, rpc-encoded, doc-literal, doc-literal wrapped), the challenges of mapping XML-schemas to different type systems as well as the impact of WS-Interoperability (WS-I).
· A proposal how to build Web Services using VS.NET 2003
We’re going to apply some of the discussed concepts and create a connected system using the current available tools. By following the contract first approach, we start with the entity and message design and continue with the service provider and consumer implementation.
Hope to see there…