Bryan, A registry manages metadata about its objects (e.g. wsdl file), and acts as a middleman between client and content. The content MAY be stored in a local repository managed by the registry software, and it may not. Content may reside elsewhere. For this reason, there is a important distinction maintained between a registry and a repository. A registry object is really just a glob of XML describing content. Regards, Matthew MacKenzie . Sr. Architect . Adobe Systems On 20-Jul-04, at 6:43 AM, Bryan Rasmussen wrote: > > As the subject line says; sure a repository stores objects and a > registry > lists services, but if in listing services it provides say a wsdl for > interacting with those services, isn't it really acting as a wsdl > repository? > > what if we have three entities: > > a > b > and c > c provides a service that b wants to use, a has a directory of > services and > wsdls for all those services, b uses a's directory and wsdl for > important > connection info on how to connect to c because a trusts b to keep c's > info > up to date. At that point it seems to me that the wsdl is an object in > its > own right. > > Is this a reasonable argument on my part? > > The ebxml-dev list is sponsored by OASIS <http://www.oasis-open.org> > The > list archives are at http://lists.ebxml.org/archives/ebxml-dev/ > To subscribe or unsubscribe from this list use the subscription > manager: > <http://www.oasis-open.org/mlmanage/> > The ebxml-dev list is sponsored by OASIS <http://www.oasis-open.org> The list archives are at http://lists.ebxml.org/archives/ebxml-dev/ To subscribe or unsubscribe from this list use the subscription manager: <http://www.oasis-open.org/mlmanage/>
<<attachment: winmail.dat>>