The Mono team starts to implement the WSE (Web services Enhancements) from Microsoft for a proof-of-concept implementation of the Web services Architecture (WSA aka GXA) initiative.
Just wondering whether they could stand the pace of the XML Messaging team in Redmond ... and furthermore, nobody told them that WSE is a moving target?
Mein Freund Christian Nagel hat es mal wieder möglich gemacht. Von morgen, Donnerstag, bis Samstag befinde ich mich auf einer kleinen Österreich-Tour, um Vorträge für INETA .NET User Groups in Graz und Klagenfurt zu halten.
.NET User Group in Graz:
Thema: "XML Web Services: Was Sie ausser [WebMethod] noch wissen müssen"
Abstract: Die Geschichte ist eigentlich schnell erzählt: Web Servicves drehen sich nicht (ausschliesslich) um Methodenaufrufe auf entfernte Objekte. Bei Web Services dreht es sich um Nachrichten! Die Einfachheit der Entwicklung und Nutzung von XML Web Services in .NET, die durch das [WebMethod]-Attribut manifestiert wird, verwischt leider einige wichtige Tatsachen und Umstände. In diesem Vortrag soll der Vorhang gelüftet werden.
Sie lernen einige Interna der Web Services Runtime (ASMX) in .NET kennen und werden sehen wie man eigene Erweiterungen dafür programmiert - client- wie serviceseitig. Und immer mit dem Hintergedanken, dass wir hier über XML-basierten Nachrichtenaustausch reden ...
Highlights: ASMX Stack in .NET, wichtige Attribute, wsdl.exe, SoapExtension, SoapExtensionReflector, ServiceDescriptionImporter, ServiceDescriptionReflector, WSE
.NET User Group in Klagenfurt:
Thema: "Anwendungen, Plattformen, Prozesse: Integration mit XML Web Services auf dem .NET Framework"
Abstract: Unsere heutige IT-Landschaft ist so bunt wie das sprichwörtliche Chamäleon. Unzählige Plattformen, Anwendungen und vor allem Geschäftsprozesse tummeln sich in einem typischen Unternehmen. Mit XML Web Services versucht man nun, einige der Integrationsprobleme besser und vor allem kostengünstiger in den Griff zu bekommen. Und bekanntermassen macht das .NET Framework von Microsoft eine besonders gute Figur bei der Erstellung und nutzung von Web Services. Lernen Sie in diesem Vortrag die technischen Grundlagen und sehen Sie einige Beispielanwendungen, die den Einsatz von XML Web Services verdeutlichen.
Highlights: XML, XSD, SOAP, WSDL, UDDI, Service Oriented Architectures, ASMX Stack in .NET
The OASIS XML Cover Pages report that the protagonists of WS-Coordination and WS-Transaction have updated their specs to make the distinction between atomic (ACID) transactions and long running business activities more explicit:
A revised version of the Web Services Coordination (WS-Coordination) specification has been published, together with a new Web Services Atomic Transaction (WS-AtomicTransaction) specification. A third specification Web Services Business Activity (WS-BusinessActivity) is to be released separately to complete the new three-part Web Services Transaction framework from Microsoft, BEA, and IBM. WS-AtomicTransaction "replaces part I of the WS-Transaction specification released in August 2002; the specification titled WS-BusinessActivity will replaces part II of WS-Transaction. WS-Coordination "defines the protocols for creating activities, registering in activities, and transmitting information to disseminate an activity. WS-Coordination provides an extensible framework in which participants can join in activities enabling the coordination of distributed applications." WS-AtomicTransaction "defines the Atomic Transaction coordination type and is appropriate to use when building applications that require a consistent agreement on the outcome of a short-lived distributed activity, where strong isolation is required until the transaction completes." WS-BusinessActivity "defines the Business Activity coordination type. It is appropriate to use when building applications that require a consistent agreement on the coordination of a distributed activity, where strong isolation is not feasible, and application-specific compensating actions are used to coordinate the activity."
The new specs can be found e.g. on Microsoft's server, but the WS-BusinessActivity spec does not yet show up:
Transaction Specification Index Page
WS-Coordination defines the protocols for creating activities, registering in activities, and transmitting information to disseminate an activity. WS-Coordination provides an extensible framework in which participants can join in activities enabling the coordination of distributed applications. Activities can support arbitrary behaviors expressed in terms of protocols including agreement coordination behaviors. Such coordination protocols are used to support a number of applications, including those that need to reach consistent agreement on the outcome of distributed transactions. The framework enables existing transaction processing, workflow, and other systems for coordination to hide their proprietary protocols and to operate in a heterogeneous and federated environment. Additionally, this specification describes a definition of the structure of context and the requirements for propagating context between cooperating services.
WS-AtomicTransaction defines the Atomic Transaction coordination type. It is appropriate to use when building applications that require a consistent agreement on the outcome of a short-lived distributed activity, where strong isolation is required until the transaction completes. This specification replaces Part I (AT) of the previously released WS-Transaction specification.
WS-BusinessActivity defines the Business Activity coordination type. It is appropriate to use when building applications that require a consistent agreement on the coordination of a distributed activity, where strong isolation is not feasible, and application-specific compensating actions are used to coordinate the activity. This specification replaces Part II (BA) of the previouslyreleased WS-Transaction specification.
Disclaimer: All information assembled in this posting are collected from the session titles and abstracts for PDC 2003 and other official information from other bloggers. I am not violating anything here :-)
The magic word 'Indigo' has been speculated (very weirdly) about by many unauthorized and authorized, because very involved, persons in blogosphere. For now, it seems like Indigo has the aim to be an integrated, extensible framework for distributed applications on the .NET platform - but with support for a wide range of distributed topologies like in-process, cross-process, intranet and Internet. Following the big Web services wave, Indigo is based on the WSA (formerly known as GXA) protocols and specs to achieve the best possible interoperability with other vendors like IBM and other partners. Maybe Indigo will finally achieve it to make it easier to build distributed applications by supporting a wide range of messaging patterns (think of request/response, asynchronous, P2P, etc.).
Messaging bus - this seems to be the most appropriate word to apply here. We actually do not have to be visionary to recognize that Indigo will be all about messaging, messaging, and perhaps ... messaging.
We should expect to see intrinsic and easy to use functionality for
- Asynchronous messaging
- Call context instead of stressing on the concept of object context
- Contract based loosely coupling (with extensibility and evolvement in mind)
- Managed classical OTM functionality as can be found in COM+ today (read: transactions and friends)
- Several stacks (or better [sub] frameworks?) like networking, security, messaging, serialization and the like
- ... a lot more of cool and interesting stuff we will all hear about in L.A. ...
Indigo should be delivered as part of Longhorn (?) and could be an internal part of the system as COM+ is today part of Windows 2000 and higher.
So for now it looks like all the apparently unrelated information that stumbled through the blogging world in the last few weeks to months about schemas, type, versions, loose coupling and all this stuff have had the big plan in mind ...
We all should be very excited and looking forward to L.A.
Cheers.
Don
Smith's article about WS-Security Drilldown in Web Services Enhancements 2.0 just
showed up on MSDN's Web services Developer Center.
How to use Web Services Enhancements 2.0 to implement security, trust,
and secure conversations in Web services architecture. Also covers the
security-related changes from Web Services Enhancements
1.0.
It explicilty covers different areas and levels of Web services
security:
SOAP Messaging
WS-Security Specification
WS-SecurityPolicy
Specification
WS-SecureConversation
Specification