[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: 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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]