OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

uddi-comment message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: Re: [uddi-comment] Best practice: locating a web service access


The current UDDI/WSDL best practice (contribution from uddi.org to OASIS 
TC) addresses the issue.

http://uddi.org/pubs/wsdlbestpractices-V1.07-Open-20020521.pdf

In short, the bindingTemplate/accessPoint is used.


- sam

Paul Sterk wrote:
> Hi,
> 
> Is there a best practice for determining the address location or
> access point of a web service when using UDDI and WSDL?  To elaborate:
> in UDDI, the access point for a web service is contained in:
> 
> <bindingTemplate serviceKey="" bindingKey="">
>         <description></description>
>         <accessPoint URLType="http>http://localhost:8080</accessPoint>
> 
>                                     ...
> </bindingTemplate>
> 
> This information is also located in the WSDL document:
> 
> <wsdl:service name="">
>         <soap:address location="http://localhost:8080/>
>                                     ....
> </wsdl:service>
> 
> So, the question is when the web service proxy client goes to the
> registry to find the updated location, should it check the binding
> template or the WSDL file?  Is there a best practice in this area?
> 
> Thanks,
> Paul




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Powered by eList eXpress LLC