CARVIEW |
Select Language
HTTP/2 200
date: Tue, 07 Oct 2025 08:02:33 GMT
content-type: text/html
content-encoding: gzip
last-modified: Thu, 20 Jul 2023 23:26:49 GMT
cache-control: max-age=2592000, public
expires: Thu, 06 Nov 2025 08:02:33 GMT
vary: Accept-Encoding
access-control-allow-origin: *
x-request-id: 98abe079dd8a0bc9
strict-transport-security: max-age=15552015; preload
x-frame-options: deny
x-xss-protection: 1; mode=block
cf-cache-status: MISS
set-cookie: __cf_bm=wewvHVh065AzcwiyWj.NXdBCJ7PM341rqHyssVMOYq4-1759824153-1.0.1.1-kvKOEbChjEEiVtl77vPL50xroEl45V8U4WHN0_b512Mds.mk9Nqg0FAE8i8dPDuNeXHx010qu151HCcaSv6R7RbydKnZK77RkAnTMIED8JY; path=/; expires=Tue, 07-Oct-25 08:32:33 GMT; domain=.w3.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98abe079dd8a0bc9-BLR
alt-svc: h3=":443"; ma=86400
Issue: should WSDL be able to describe an operation with *anything* in the message? from Jacek Kopecky on 2004-02-18 (www-ws-desc@w3.org from February 2004)
Issue: should WSDL be able to describe an operation with *anything* in the message?
- From: Jacek Kopecky <jacek.kopecky@systinet.com>
- Date: Wed, 18 Feb 2004 15:51:24 +0100
- To: WS-Description WG <www-ws-desc@w3.org>
- Message-Id: <1077115884.26488.60.camel@localhost>
Hi all, I stumbled upon a scenario the other day where I'd like to be able to describe an endpoint with a single logical operation ("accept" or "notify" or something) that can accept any SOAP message. Somebody wanted a WSDL for this endpoint and I found out that WSDL 1.1 with a single message part of the type xs:anyType is not supported in doc/lit, and in fact in WSDL 2 such a thing cannot be accomplished at all because every message has exactly one XML element and the SOAP binding puts precisely that element as a child of soap:Body. Should WSDL be able to describe such an endpoint? I think so because it is common in various message sink situations - a router, a topic, generic notification sink etc. I can see a simple solution that would state that if a GED is not specified for a message, it can be everything. There are other alternative solutions, but this seems the simplest and least bad. Sorry about bringing this up so late, Jacek Kopecky Systinet Corporation https://www.systinet.com/
Received on Wednesday, 18 February 2004 09:51:30 UTC