On Thu, Dec 4, 2008 at 8:18 AM, A W <[EMAIL PROTECTED]> wrote: > It will help understanding the concept of finding applications automatically > because it is simply uses a supply chain example. Pleas take a look. > > > > IBM Dynamic process is a suite contains a set of collaborative, role-based > capabilities that enable customers to model, simulate, execute, rapidly > change, monitor and optimize core business processes. > > > > Any business Function needs an interface. Interfaces are defined using WSDL. > > If you take a look at UDDI technology, a provider usually publish its WSDL in > the UDDI registry. > > > > The convention for publishing WSDL-based web services in a UDDI registry can > make UDDI effective for doing dynamic discovery of web services at runtime. > > There have been attempts to define specifications for web services discovery. > WS-Inspection and WS-ServiceGroup. > > IBM is a key player behind all web services standards and its implementation.
I'm very familiar with the use of UDDI and I've seen samples similar to the WS-I one: http://www.ws-i.org/SampleApplications/SupplyChainManagement/2003-12/SCMArchitecture1.01.pdf . And as Michael observed, this same automated service discovery capability was spec'ed out, and I'm sure demo'ed, back in the CORBA days. I've just never seen it used in production in any significant application. You mentioned something about a "magenta" supply chain. Is that a particular application using such a discovery approach? Could you provide more details. I'm looking for real production use of this technique. -- Nick PS The WS-I sample application doc references the public UDDI registries that IBM, Microsoft, and SAP put up a long time ago. They shut them down a couple of years ago because no one used them except for demos. That's my point.
