RE: [uddi-spec-comment] WSDL and hostingRedirector

["George Datuashvili" <George.Datuashvili@Siebel.com>]

Thanks, in V3 then one would use accessPoint(useType=bindingTemplate).
But what determines whether the use case is "normal" or not? As more
people will try to use local UDDI registries for fully dynamic
invocation, I would kind of expect this case to be pretty normal :)

Also it's unclear how web service policies should be applied in case uf
redirection. Does client have to get attached policies from the first
service, second service, or both?

Thanks,
Gia
 

> 
> -----Original Message-----
> From: Anne Thomas Manes [mailto:anne@manes.net] 
> Sent: Saturday, July 26, 2003 6:36 AM
> To: George Datuashvili; uddi-spec-comment@lists.oasis-open.org
> 
> George,
> 
> Use of hostingRedirector is not the normal case, so we didn't 
> include it in the technical note. The technical note is 
> scoped to address best practices for normal operations.
> 
> hostingRedirector is still supported in V3, it's just the 
> format is a little different. Rather than having separate 
> elements in a choice group (use either <accessPoint> or 
> <hostingRedirector>), in V3 we added a useType attribute to 
> <accessPoint> that supports a number of different values, 
> including "endPoint", "wsdlDeployment", "bindingTemplate", 
> "hostingRedirector", and "other". (See [1]) The 
> "bindingTemplate" and "hostingRedirector" values replace the 
> V2 <hostingRedirector> element.
> "bindingTemplate" supports simple indirection (which 
> addresses your use case below), and "hostingRedirector" 
> supports redirection.
> 
> [1] 
> http://uddi.org/pubs/uddi-v3.00-published-20020719.htm#_Toc42047544
> 
> Best regards,
> Anne
> 
> ----- Original Message -----
> From: "George Datuashvili" <George.Datuashvili@Siebel.com>
> To: <uddi-spec-comment@lists.oasis-open.org>
> Sent: Friday, July 25, 2003 6:28 PM
> Subject: [uddi-spec-comment] WSDL and hostingRedirector
> 
> 
> > Just read Using WSDL in a UDDI Registry, Version 2.0...
> >
> > One unclear thing is the pattern of using hostingRedirector (which 
> > seems to be deprecated by accessPoint in 3.0). Or some 
> other mechanism 
> > to allow "pluggable services":
> >
> > Imagine use case when we have local UDDI registry, and 
> clients query 
> > it at runtime to figure out what port/address to use to 
> invoke a service.
> > In reality, there are cases when not only client doesn't know the 
> > address, but it doesn't know which service to use. It only knows 
> > portType/tModel. Querying for ANY service that has matching 
> > bindingTemplate (as often described in introduction-to-uddi 
> documents) 
> > and using it is not desirable, since there might be 
> multiple services 
> > that implement the interface, but system administrator 
> might want to 
> > specify which one should be used by all clients today.
> >
> > One possible solution for this might be a dedicated dummy 
> service in 
> > UDDI with known name (or key) that clients will use to get 
> > hostingRedirector value. Then clients will do another query to the 
> > determine actual endpoint.
> >
> > Is there a better way to do this?
> >
> > Thanks,
> > Gia
> >
> >
> >
> > 
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: 
> > uddi-spec-comment-unsubscribe@lists.oasis-open.org
> > For additional commands, e-mail:
> uddi-spec-comment-help@lists.oasis-open.org
> >
> >
> 
> 
> 
>