"The way we organize our computer files mirrors the office file cabinet example. When looking for the minutes from a year-old client meeting, you'd first find the folder with the client's name, look for the Meetings subfolder, and then perhaps sort that folder's contents by date. Of course, another person might organize it differently: he might have a Work folder, then a Meetings folder, inside which he would group items by client. That difference can be problematic when you're on vacation and your coworker urgently needs that meeting note. Thus, for important files, offices typically allocate shared directories, or network drives, and create policies on where and how you should save files."
"Most business-to-business interactions are collaborations between two parties who engage in a partnership. These business partners share a registry, often in the form of a Web-based service. A registry typically functions as electronic Yellow Pages, where information about businesses and the products and services they offer are published and discovered. A registry can also serve as a database or store shared information, information that can encompass anything. A registry can also work as an electronic bulletin board in which the partners share information in a dynamic and ad hoc fashion. As described in the JAXR specification, information examples include generic event notification, price changes, discounts, and promotions."
"With this basic understanding of the tModel, let us investigate, using a UML diagram, the relationship between a binding template and tModels. As I have suggested earlier, this should lead us to a direct understanding of how a binding template achieves the "how to invoke a service" requirement of UDDI."
"Many data formats are being used in the enterprise world that make it difficult for businesses to collaborate with one another at the application level. Web services enable interoperability through a set of XML-based open standards. Businesses can describe their Web services on the Internet using an XML-based language, such as the Web Services Description Language (WSDL), or simple plain text, and list them in an XML-based registry such as Universal Description, Discovery, and Integration (UDDI), or the electronic business XML (or ebXML) Registry. But since the formats of these XML-based registries are different, developers must study each of them carefully and in detail. Luckily, however, Sun has pioneered the JavaTM API for XML Registries (JAXR), which can be used to access any of the most widely adopted XML-based registries. With JAXR, you don't need to worry about the differences between UDDI and the ebXML Registry."
"The recent release of the Java Web Services Developer Pack (JWSDP)?a collection of tools and APIs for building Web Services based on the Java 2 Enterprise Edition (J2EE)?includes an API tailored for registry interaction. The Java API for Registries (JAXR) provides a convenient way for Java developers to use a single simple API to access a variety of XML registries including UDDI and ebXML. In this article, we explore the role played by UDDI and ebXML registries in the Web Services world, and examine some of the details of working with the JAXR to connect with these and other registries."
