In article <001201c28072$44aa1720$0a01a8c0@T30COLGRAVE>, [EMAIL PROTECTED] (John Colgrave) wrote:
> ----- Original Message ----- > From: "John Francis" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Cc: <[EMAIL PROTECTED]> > Sent: Wednesday, October 30, 2002 12:31 PM > Subject: Why don't WSDL URLs in UDDI contain 'service' elements? > > I'm trying to knock together some code to query a UDDI registry and > > call a > > Web Service given it's WSDL URL. I've got the latter part of the > > problem > > working (calling the Web Service) using some of the WSDL URLs listed > > on > > the XMethods site. However, if I navigate to the WSDL overview > > document > > URL via the UDDI registry I seem to get a different WSDL URL with no > > service element. The WSIF code (modified from the DynamicInvoker) > > sample > > fails because this WSDL URL doesn't contain any services. > > > > I don't understand why the UDDI registry doesn't contain a pointer to > > the > > URL with the service element, but a different WSDL file. > > The UDDI Best Practice for WSDL [1] assumes that you have two WSDL > files: > one with the portType and binding(s) and the other with the service. > Only > the first is referenced in UDDI. The address information is defined by > the > bindingTemplate accessPoint. Thanks for the reply, John. I think I just about figured that out yesterday evening. Would I be correct in thinking that I could contruct my own Service (ServiceImpl) object from the bindingTemplate accessPoint information and pass this to WSIF's ServiceFactory along with the tModel WSDL definition and eventually end up with a Port that I could invoke on dynamically? John Francis
