Re: binding/service question

Nicolas,

Yes, you can and should define one binding and multiple services. Here's 
how to do it.

1. Create the common binding wsdl, e.g. binding.wsdl and put it on a 
common server.
2. At each node, create a service.wsdl that uses the binding and defines 
its own endpoint. It should import binding.wsdl.

A client application can use a common proxy for binding and then set the 
endpoint for each service.

Arthur Ryman,
IBM Software Group, Rational Division

blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca



"Nicolas Mailhot" <nicolas.mailhot@laposte.net> 
Sent by: www-ws-desc-request@w3.org
04/06/2006 10:56 AM

To
www-ws-desc@w3.org
cc

Subject
binding/service question










[ I already sent this to www-ws@w3.org but maybe this list is more
appropriate]

Hi,

I have a system where several nodes will export the same web services
interface. The technical interface will be the same, but the datastore
behind different. Another node will connect to all these systems at once
and collect their info (this is not a load balancing setup, you can not
substitute one node for another).

Can I define a single wsdl binding and only differentiate the nodes at the
service level (since it's all the same technical interface) or must I use
different services and bindings (since on the functionnal level every node
is distinct) ?

I'd rather do the first thing since it's more robust (less duplicate info)
but I have the horrible feeling tools will get confused if I do so.

What is the right thing to do in this case ?

Regards,

-- 
Nicolas Mailhot



-- 
Nicolas Mailhot