XML

SOAP

WSDL

Introspection Service, in Zope and Plone you can expose services and you don't need to transfer the notion od documents in another language. Things become 'self describing'


Service oriented Architecture

* Individual services, decouple your application into disjoint services enables you to scale your software. Messages can discover where to find a particular interface they might need.

What is the difference from xml-rpc?

* The description of types is sometimes complex.

UDDI, SOAP, WSDL

Generation One Web Services

Usually 99% of the time you can assume that the web server is doing the right thing ;-)

* XPath

* XML Schema Definitions (XSD)

The technologies around kind of mismatch and we'd need some glue to integrate all components we are talking about. We have messaging specifications, built to build other specifications. A lot of different approaces have been taken. It is complicated stuff. We can not efford to ignor the efforts of big companies any more, so we have to look at standards that are out there.

Composition would mean more machines and workflow, conditions of data.

Plone has to be percieved as a component among other components regarding that topic. We will adress enterprise customers with technology like that.

There is not even closure on models and we have to agree on subsets.

WS-I Basuic Profile

This is the best we can go to shoot for to become more interoperatible. The work shown here can easily interoperate with a lot of the software mentioned.

Q: XML-RPC fundamental difference?

Q: Specifications WWW2C loves to put specifications
A: They break down specifications into smaller peices that are not stalled by long time it takes to evolve another version, like it is the case with html.

Q: I came from J2EE and happend to see Plone, the first thing I wanted to do is making J2EE software with Plone, but there was nothing but xmlrpc.
A: If you don't know where your needs lie or you don't know how to split down the problems...

We need something that describes types, it is known as SOAP encoding. It is designed to do argument marshalling. As ambition as it was to do xmlrps plus plus it was not really the solution peoiple needed. You can not really map types between languages anyways. There are a lot of recommendations... Minus One, empty tags, ...

It turns out that there is another approach, too:

Document focused approach: Document literal encoding

'When you already have XML or don't have anything'

This is sort of current best practice.

If we ship objects across the wire we can strip them into strings and numners and marshall them like this, but what we need is ways to talk about how to get the whole document over the wire.

Object Oriented

* Traversioal results, methods

* One way adressing web services: particular objects with methods

* Catalog, finding means triggering actions

Service Oriented, Service Publishing

* Services become your entry point to gather objects that implement a specific caracteristic

[...Paul Everitt hints Ben to hurry up...]

WSDL is already fully supported, it is generated automatically.

There are convenience methods

[...code is shown on the screen...]

[...screenshot of a prototype like client...]

[...introspected methods can be invoked, and seen...]

Integration should be seamless...

Q: What is the curren support for SOAP lib
A: CSI, Java .net, is the question for a client? The models are slightly different, but they share a WSDL base. To be honest: I use a patched version of CSI

Q: The code is part of Archetypes?
A: It is in a private repository. It ios tested now, then we are going to publish it.

All you do when you introspect objects...
You have to be very carefull when you marshall...

[...Paul Everitt needs to announce the next talk, the schedule is tight...]

Maybe there should be a lightning talk Ben could give for us...