W3C home > Mailing lists > Public > www-ws-desc@w3.org > October 2003

RE: PROPOSAL: Drop interface/operation/(input|output)/@headers

From: <paul.downey@bt.com>
Date: Tue, 21 Oct 2003 08:54:28 +0100
Message-ID: <2B7789AAED12954AAD214AEAC13ACCEF0FFF1C86@i2km02-ukbr.domain1.systemhost.net>
To: <alewis@tibco.com>, <sanjiva@watson.ibm.com>
Cc: <www-ws-desc@w3.org>

+1 

We've encountered problems from header fields defined in WSDL 1.1. Several existing toolkits generate a holder Java/C# class for header values defined in the soap:binding. This has places header processing in application-layer code and causes much confusion.  

Using properties/features for headers hopefully communicates that these fields belong to layer 6 and below ..

Paul

-----Original Message-----
From: Amelia A. Lewis [mailto:alewis@tibco.com]
Sent: 20 October 2003 19:15
To: Sanjiva Weerawarana
Cc: www-ws-desc@w3.org
Subject: Re: PROPOSAL: Drop interface/operation/(input|output)/@headers

+1.

I'll add to this, hopefully provoking Glen into offering greater detail
and explanation, that headers can be specified for use via the
properties/features component of WSDL, and that stipulating their
existence in that fashion is far more comprehensible.

Amy!

On Mon, 20 Oct 2003 23:59:45 +0600
Sanjiva Weerawarana <sanjiva@watson.ibm.com> wrote:

> [snip]
Received on Tuesday, 21 October 2003 03:54:30 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:58:27 GMT