[prev in list] [next in list] [prev in thread] [next in thread] 

List:       uddi4j-general
Subject:    RE: [Uddi4j-general] RE: uddi and wsdl
From:       "Agrawal, Anuj (Anuj)** CTR **" <agrawal () lucent ! com>
Date:       2001-10-09 16:04:15
[Download RAW message or body]

Graeme -

This was an excellent summary!! Thanks so much for the overview as well as
the URL pointers.

Anuj.

> The best references that I have come across to tie these 
> subjects together
> are:
> 
> http://www.uddi.org  contains a link to a best practices doc:
> http://www.uddi.org/pubs/wsdlbestpractices-V1.05-Open-20010625.pdf
> 
> and the IBM developer-works site has a couple of links with 
> more specific
> examples and scenarios:
> http://www-106.ibm.com/developerworks/webservices/library/ws-wsdl/
> http://www-106.ibm.com/developerworks/webservices/library/ws-w
> sdl2.html
> 
> A summary might be: The information in the WSDL doc actually 
> needs to get
> broken out and stored in the various data structures in the 
> business entity
> hierarchy and the tModel. The tModel describes the service 
> interface (spec)
> and the businessEntity hieracrchy describes any service instances that
> actually implement (support) that interface. Both of those sets of
> information happen to be stored in 1 WSDL doc There's nothing 
> (yet) that
> automatically breaks up a WSDL doc and publishes the right 
> bits of WSDL
> information to the right places in UDDI.
> 
> I'm sure everything will be clearer once you've seen that 
> material, but to
> address your points specifically:
> 
> 1. The information in a wsdl doc can be submitted (actually 
> published) to a
> UDDI registry, assuming you have registered your business 
> name (entity)
> there and have an account. But that server will not do any 
> processing of the
> information, other than maybe forward it to other registries in its
> federation. All field population needs to be done by yourself 
> via the API. 
> 
> 2. UDDI4J is a Java API that implements the UDDI 1.0 spec, 
> allowing folks
> like you & me to browse and publish UDDI registries from our 
> Java code. WSDL
> is a content description, and it's the information in the 
> WSDL doc, and
> probably a URL to the doc itself, that actually gets 
> published to UDDI. So
> the UDDI API knows nothing about WSDL. 
> 
> 3. Those references should shed light on this one. The 
> registry will not do
> anything with the WSDL file. The approach suggested is that 
> the URL of the
> WSDL doc is stored in the OverviewURL attribute in the 
> OverviewDoc of the
> tModel. 

[prev in list] [next in list] [prev in thread] [next in thread]