UDDI Development Guide under Windows.net
Mood
2002.02.28
Article Type: in-depth
Difficult Level: 5/9
Version: 2.03
[Consessment]
Ok, we have completed the entire operation of the second step. However, in the above operation, we can see [Jan 01] has a single access point problem that discusses the WebServices of Visual Studio.NET. Similarly, you can also refer to the document resource below [BCE 01], [FNV 01], [FNV 02] to learn more about the UDDI data structure and standard information, which is the concept you must program in the future, but I always It is considered that this document is full of pain and trouble, and it is desirable to at least one vivid starting point for the above operation map.
After we moved to the VSDOTNET machine, we will make an example of finding and programs, and finally we will discuss the problem of UDDI support under Add Webservice References under Visual Studio.NET. First we enter http: // datacenter / uddi in the VSDOTNET IE window, we can see the familiar IE window mentioned in the second step (before this window, we need a license verification of the DATACENTER machine. ) Simple test, the result and the same in Datacenter. Since this machine we installed UDDI SDK and Visual Studio.NET, we can try Samples -> UDDI Explorer in SDK. Here, you need to get enlighten from [Jan 02]. From his article, you can find the link between http://localhost/uddi/api/inquire.asmx in his article, and take a closer look at the UDDI installation directory you will find this asmx Existence, in fact, it is a Webservices inside, providing some interfaces such as FindBinding, GetServiceDetail, GetBindingDetail, and see what it wants to do. Below is the result of running, it looks good, everything is smooth.
I don't know if you have the same idea as I: I think as long as WebServices registered in UDDI, in the Add Web References in Visual Studio., It can be automatically identified by IDE and generate an agent class. [See 01] did not introduce this detail, but after [See 01] was completed, in Visual Studio.NET, it was the same as we used to previous, and the generated proxy class is indeed valid. I follow the documentation. The description is done, the result is successful. But for Web Services, which is registered above, doing similar operations.
Similarly, I went to the IBM's UDDI website to do the same operation, and Visual Studio.net still can't perceive the Web Services that has been searched in [See 01] and generates a proxy class.
Conclusion Microsoft has made some special processing, making it easier to support Visual Studio.net, because when you click on the registration entry, it is easy to locate it to http://uddi.microsoft.com/visualstudio/vsserviceResults.aspx Businesskey = xxxxx link, thus being found to generate a proxy class by Visual Studio.net. It is easy to be confused by Microsoft's developers, and it is considered that UDDI registration and generating agency class is a category; the manual manual is clearly knowing that you need to enter two lines of different commands. In fact, outside the IDE or manual programming, you need to have a clear understanding and correct concept of the two and the entire UDDI process.
In addition to UDDI, there is another specification of WS-Inspection, hoping to cause your attention and interest. Although it is currently only supported by Microsoft and IBM, but in fact, WS-Inspection is supplemented to UDDI, so that developers will easier to like it. As for the relationship between WS-Inspection and UDDI, I want [NAG 01] to be a more clear instructions, but also a piece of writing skills, you can do two abstract concepts without a line of code. Next:
Next, you need to continue your UDDI, which is joy is that UDDI itself is constantly developing and expanding. No matter how much API, the API still still feels heavy and need to gas. If you create the INTERNET and Web Services a perceived application is our future task, then familiarity and proficiency These are the necessary choices.
As for the program-level registration interface and programming, you can download [UDDI SDK 2.0 Beta] Microsoft, while Java users can start from the recommendations in [SIL 01], thanks to Microsoft and IBM, because they are not them, the developers are still unable to concentrate To an important design phase.
As for the test environment, both IBM, Microsoft, HP, and SAP four companies provide public UDDI test environments, and Press [Jan 01], IBM and Microsoft will copy their respective entries within 24 hours. In the Windows.Net environment, your test will be more convenient and easy, and Windows.net itself makes me fascinated (Haha).
Related resources and documents:
[Jan 01] Karsten Januszewski, using UDDI Web Services Description and Discovery (Part 1), Microsoft Corporation, 2001.10.03
[See 01] Scott Seely, using UDDI Web Services Description and Discovery (Part 2), Microsoft Corporation, 2001.10.17
[Jan 02] Karsten Januszewski, UDDI, Microsoft Corporation, 2001.12 at runtime
[BCE 01] Peter Brittenham, Francisco Cubera, Dave Ehnebuske, Steve Graham Understanding WSDL - How to Publish and Find WSDL Services Description, IBM Corporation, 2001.09
[FNV 01] Data Model of Chai Xiaoxi, UDDI Registration Information, IBM Corporation, 2001.06.07
[FNV 02] Chai Xi Road, TMODEL System and Public TMODEL, IBM Corporation, 2001.06.22
[NAG 01] William A. Nagy, Keith Ballinger, WS-INSPECTION and UDDI, IBM Corporation, 2001.11
[SIL 01] ALFREDO DA SILVA, Service Registration Agent: A Advanced API, IBM Corporation, 2001.11
[UDDI SDK 2.0 Beta]
especially:
The above software, the citation has indicated that the source and owner, respect the copyright and the relevant terms.
This article 9CBS signature start, reprint, or adaptation, please indicate the author and the source. If there is a problem, please send an email to new2001@msn.com
The above text and pictures involve other people's privacy and personal rights, all texts and pictures are only used for internal communication and do not make any news published and commercial purposes.
