RE: Multiple endpoints with the same interface

The WG explicitly decided to keep the status quo from WSDL 1.1. As you
note, you can work around this with multiple services.

Alternatively, you may be interested in the solution to R085 and/or
R131:

R085: The description language SHOULD allow describing Messages that
include references (URIs) to typed referents, both values and Services.
(From PP. Last discussed 11 April, 2002.)

R131: The WG SHOULD define components that may be used within Messages
to refer to other WSDL components. (From DO. See also R085 and R120.
Last discussed 6 Feb 2003.)

http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/requirements/ws-desc-re
qs.html (ed copy)

A recent thread on this latter point begins at
http://lists.w3.org/Archives/Public/www-ws-desc/2003Apr/0035.html.

--Jeff

> -----Original Message-----
> From: www-ws-desc-request@w3.org [mailto:www-ws-desc-request@w3.org]
On
> Behalf Of Kenneth Chiu
> Sent: Tuesday, April 15, 2003 10:27 PM
> To: www-ws-desc@w3.org
> 
> 
> We are working on a mapping from the U.S. Dept. of Energy
> Common Component Architecture (CCA) to WSDL.  CCA components
> may have multiple ports of the same type, each representing
> a different "instance".
> 
> Because WSDL 1.1 stated that multiple ports of the same
> portType provide "semantically equivalent behavior" we have
> been mapping each CCA port to a separate service.
> 
> What is the current thinking for 1.2?  The latest draft
> doesn't seem to have any guidance on the semantics of
> multiple endpoints of the same interface in one service.
> 
> Kenneth Chiu
> Indiana University

Received on Wednesday, 16 April 2003 16:17:49 UTC