Return-Path: Delivered-To: apmail-ws-axis-user-archive@www.apache.org Received: (qmail 44998 invoked from network); 17 Oct 2007 08:27:56 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 17 Oct 2007 08:27:56 -0000 Received: (qmail 6873 invoked by uid 500); 17 Oct 2007 08:27:36 -0000 Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 6856 invoked by uid 500); 17 Oct 2007 08:27:36 -0000 Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-user@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-user@ws.apache.org Received: (qmail 6845 invoked by uid 99); 17 Oct 2007 08:27:36 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Oct 2007 01:27:36 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of andreas.schultz@gmail.com designates 209.85.146.181 as permitted sender) Received: from [209.85.146.181] (HELO wa-out-1112.google.com) (209.85.146.181) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Oct 2007 08:27:40 +0000 Received: by wa-out-1112.google.com with SMTP id k22so2984794waf for ; Wed, 17 Oct 2007 01:27:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=Hqo8ZR3DyMMVHQ7ZHsOb+ZJamb0i/o2cJH45l8A4tGM=; b=Bf7JcGcd9leLLzGu8/GX8gA+MedmU0ZdRT4dGSXT/11XNg8s/wKqVqRZOZSaogyCD7M9r0aAM2kWEtt8JADLWnq9L1FAJ3PUMgk9N9GQfE/d38IPS6iKL/RAp3LXzXkk4aBHy01eUKGSOpiYNcTo9RT7pl/dw8NkgVFhsEG6PTk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=XT4MpA5OdS7MK2cee+z0XP+jOw60UP7a79URZLTgYOWEZfCKCJ6IXpXD7IjGcC4NNXcZ5Jb3DBZmD2VN6uErXnXC3gPzIGEHSnwTdMjBnu9AHcPMKjkViqtggVl2cAVvxLx2s4wh5Wk22luwntNrZbB+3Oum1QrKJMhaJFX4zxc= Received: by 10.114.158.1 with SMTP id g1mr9558803wae.1192609638839; Wed, 17 Oct 2007 01:27:18 -0700 (PDT) Received: by 10.115.15.5 with HTTP; Wed, 17 Oct 2007 01:27:18 -0700 (PDT) Message-ID: Date: Wed, 17 Oct 2007 10:27:18 +0200 From: "Andreas Schultz" To: axis-user@ws.apache.org Subject: Re: Axis2: howto handle custom mustUnderstand Headers In-Reply-To: <27B8FA1CA946CC4C98BC6726469AF945A9BCE0@corinthe.cgi.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <27B8FA1CA946CC4C98BC6726469AF945A9BCE0@corinthe.cgi.fr> X-Virus-Checked: Checked by ClamAV on apache.org Hi, Thanks for you help, i have it working now. It might be noteworthy that the mustUnderstand validation is executed after the inFlow is complete but before the message receiver is invoked. So doing the header processor in the invokeBusinessLogic() method of a generate ADB binding is to late. I have now written my own in flow handler that processes the incoming headers and a out flow handler that adds the headers in the response. Andreas On 10/16/07, ROSSILLE Samuel wrote: > Hi > > messageContext.getEnvelope().getHeader().examineAllHeaderBlocks() > gives you an Iterator over all the SOAPHeaderBlock of the message > > hb.getMustUnderstand() > tells you if a the SOAPHeaderBlock hb must be understood. > > hb.setProcessed() > tells Axis that your program understands a the SOAPHeaderBlock hb and has= correctly completed it's processing. > > Regards > Samuel Rossille > > -----Message d'origine----- > De: Andreas Schultz [mailto:andreas.schultz@gmail.com] > Envoy=E9: mardi 16 octobre 2007 15:54 > =C0: axis-user@ws.apache.org > Objet: Axis2: howto handle custom mustUnderstand Headers > > Hi all, > > I need to handle custom header fields that have the mustUnderstand > attribute set to true(1). > Currently such an invocation triggers a fault: > org.apache.axis2.AxisFault: Must Understand check failed for header : MyI= D > > Searching the maillinglist has turned up a references to a > MustUnderstandChecker, but i don't understand how i tell it what > header elements are supported. > > Is there a magic trick to tell axis which headers my service likes? > > Regards > Andreas > > --------------------------------------------------------------------- > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org > For additional commands, e-mail: axis-user-help@ws.apache.org > > --------------------------------------------------------------------- > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org > For additional commands, e-mail: axis-user-help@ws.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org For additional commands, e-mail: axis-user-help@ws.apache.org