From axis-dev-return-23017-apmail-ws-axis-dev-archive=ws.apache.org@ws.apache.org Fri Aug 08 05:44:39 2003 Return-Path: Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 4143 invoked by uid 500); 8 Aug 2003 05:44:37 -0000 Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@ws.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-dev@ws.apache.org Received: (qmail 4132 invoked from network); 8 Aug 2003 05:44:37 -0000 Message-ID: From: Glen Daniels To: "'axis-dev@ws.apache.org'" Subject: RE: MustUnderstand faults Date: Fri, 8 Aug 2003 01:52:07 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > We should fix this immediately - I'll volunteer to do so this > weekend. Are people OK with switching back to the > "pre-flight-check" for MU headers (my preferred fix)? After some consideration I think this needs a bit more thought, since "pre-flight"ing requires all Handler authors to include the QNames their Handlers deal with, and also requires pre-execution knowledge of all possible Handlers in the chain. These aren't really huge problems, but they are changes and need to be carefully considered. Perhaps the first step toward fixing this is putting the MU-checking handler back at the end of the SOAPService's request chain and then going further after that. --Glen