Return-Path: Delivered-To: apmail-ws-axis-c-dev-archive@www.apache.org Received: (qmail 35100 invoked from network); 29 Aug 2008 08:18:05 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 29 Aug 2008 08:18:05 -0000 Received: (qmail 52722 invoked by uid 500); 29 Aug 2008 08:18:04 -0000 Delivered-To: apmail-ws-axis-c-dev-archive@ws.apache.org Received: (qmail 52538 invoked by uid 500); 29 Aug 2008 08:18:03 -0000 Mailing-List: contact axis-c-dev-help@ws.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: "Apache AXIS C Developers List" Reply-To: "Apache AXIS C Developers List" Delivered-To: mailing list axis-c-dev@ws.apache.org Received: (qmail 52527 invoked by uid 99); 29 Aug 2008 08:18:03 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Aug 2008 01:18:03 -0700 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.68.5.9] (HELO relay00.pair.com) (209.68.5.9) by apache.org (qpsmtpd/0.29) with SMTP; Fri, 29 Aug 2008 08:17:05 +0000 Received: (qmail 58857 invoked from network); 29 Aug 2008 08:16:32 -0000 Received: from unknown (HELO ?127.0.0.1?) (unknown) by unknown with SMTP; 29 Aug 2008 08:16:32 -0000 X-pair-Authenticated: 203.115.29.239 Message-ID: <48B7B05C.3080509@wso2.com> Date: Fri, 29 Aug 2008 13:46:28 +0530 From: Danushka Menikkumbura User-Agent: Thunderbird 2.0.0.16 (Windows/20080708) MIME-Version: 1.0 To: Apache AXIS C Developers List Subject: Re: Service client options to set custom HTTP headers References: <48B78FCA.1040806@wso2.com> <48B7A08F.1050306@gmail.com> <48B7A3B4.3070406@wso2.com> <48B7AC44.9020401@gmail.com> In-Reply-To: <48B7AC44.9020401@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org > override options come into play when we reuse operation client. Say > after sending some application messages you need to override some > options. Then you create new options struct and called svc client's > set_override_options. What happens is that existing options struct > becomes parent and your override options become operations clients' > options struct. > > However I have never used this functionality. > Thanks Damitha!. I get the picture. Danushka -- Danushka Menikkumbura Technical Lead, WSO2 Inc. blog : http://danushka-menikkumbura.blogspot.com/ http://wso2.com/ - The Open Source SOA Company --------------------------------------------------------------------- To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org For additional commands, e-mail: axis-c-dev-help@ws.apache.org