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


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 ..


-----Original Message-----
From: Amelia A. Lewis []
Sent: 20 October 2003 19:15
To: Sanjiva Weerawarana
Subject: Re: PROPOSAL: Drop interface/operation/(input|output)/@headers


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.


On Mon, 20 Oct 2003 23:59:45 +0600
Sanjiva Weerawarana <> wrote:

> [snip]

Received on Tuesday, 21 October 2003 03:54:30 UTC