Abstract:
An XML registry is an infrastructure that enables the building, deployment, and discovery of Web services. To deploy and discover web service, users need to access the XML registry through a client.
The ebXML registry and repository supports two types of topologies, the client can either be a fat client or a thin client. In fat client the User interface runs on client machine whereas in thin client it run on the server and is accessible through web browser.
Along with the need for a thin client there was a file/folder metaphor within the thin client; this would be the Registry Explorer. A registry explorer like a windows explorer would present the registry as a collection of files and folders thus making it immensely easy for the client to understand the registry structure. The registry explorer would incorporate all the features for the clients use except for discovery which is part of the thin client.
Using the registry explorer the client can double click and view every detail of the object, can expand and collapse a folder, can remove, submit, deprecate objects.
