Return-Path: Delivered-To: apmail-ws-axis-c-user-archive@www.apache.org Received: (qmail 65397 invoked from network); 26 Jul 2007 11:32:58 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 26 Jul 2007 11:32:58 -0000 Received: (qmail 67760 invoked by uid 500); 26 Jul 2007 11:32:59 -0000 Delivered-To: apmail-ws-axis-c-user-archive@ws.apache.org Received: (qmail 67749 invoked by uid 500); 26 Jul 2007 11:32:58 -0000 Mailing-List: contact axis-c-user-help@ws.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: "Apache AXIS C User List" Reply-To: "Apache AXIS C User List" Delivered-To: mailing list axis-c-user@ws.apache.org Received: (qmail 67738 invoked by uid 99); 26 Jul 2007 11:32:58 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Jul 2007 04:32:58 -0700 X-ASF-Spam-Status: No, hits=2.9 required=10.0 tests=HTML_10_20,HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of s.mangelsdorf@gmail.com designates 209.85.132.246 as permitted sender) Received: from [209.85.132.246] (HELO an-out-0708.google.com) (209.85.132.246) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Jul 2007 04:32:57 -0700 Received: by an-out-0708.google.com with SMTP id c17so96362anc for ; Thu, 26 Jul 2007 04:32:36 -0700 (PDT) DKIM-Signature: a=rsa-sha1; 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:references; b=cyzF+zdHtpb7bWqEbdamX5xlBoR0sud0PoTpmKuYnXFnebtHDR2xOSmddoFwiBnI0epQVhHqwFe6on8bgNk32jnD+c35yYTqKmgtivwXqZO4QRHGVyEfK2iEKBl4U46cUW4kYArLH5o3QWSzZn0p0QYU67GkJpeiD4btdyeppYE= 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:references; b=FKc8tJQjkwd05ea7qKJSreZhQlSjfk3aSL7SJUPI4xEu67bQUR6BZUX70IbdLVC9j4kIM/vLA5YrohE9KDk+3LTDTXF4sCHolQGR6c+fpytWJs4pHpXtl2FJaAAinziBiIVz+3d5Q3gDLXP++I0Sa3XzPpOiy5tY5osqdTFYjIA= Received: by 10.100.139.12 with SMTP id m12mr1102282and.1185449556350; Thu, 26 Jul 2007 04:32:36 -0700 (PDT) Received: by 10.90.68.12 with HTTP; Thu, 26 Jul 2007 04:32:36 -0700 (PDT) Message-ID: <90ad28f40707260432v7911e1afsde6b830351d3a3d5@mail.gmail.com> Date: Thu, 26 Jul 2007 21:32:36 +1000 From: "Shaun Mangelsdorf" To: "Apache AXIS C User List" Subject: Re: [Axis2/C] Access to service context or environment In-Reply-To: <87abtj674c.fsf@etch.wso2.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_119892_7292091.1185449556319" References: <90ad28f40707252219h16fa6267w228db962efc045b5@mail.gmail.com> <87abtj674c.fsf@etch.wso2.com> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_119892_7292091.1185449556319 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi, Yes, In server side, When invoking You can get msg_ctx using that > message context you will be able to get config_ctx or config. Thanks for the quick reply. I have had a look at the echo service in samples and I can't see where the message context is used. After looking through the axis2 API more, I can see that the conf_ctx has a fair bit of configuration information in it, but it all seems specific to the axis2 environment. Is there a way to get custom configuration information into (and ultimately retrieve it from) this context struct? I also can't see a way, using the message context, to maintain state between web service calls - i.e. initialize a struct (or in my case, a C++ object pointer) and access the same object again the next time a call is made. Is this possible? It seems to be a conscious design decision that the apache environment is not visible within the service calls. Is there a way to get to the request_rec or server_rec objects created by apache, from within the service? Thanks, Shaun ------=_Part_119892_7292091.1185449556319 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi,

Yes, In server side, When invoking You can get msg_ctx using that
message context you will be able to get config_ctx or config.


Thanks for the quick reply. I have had a look at the echo service in samples and I can't see where the message context is used. After looking through the axis2 API more, I can see that the conf_ctx has a fair bit of configuration information in it, but it all seems specific to the axis2 environment. Is there a way to get custom configuration information into (and ultimately retrieve it from) this context struct?

I also can't see a way, using the message context, to maintain state between web service calls - i.e. initialize a struct (or in my case, a C++ object pointer) and access the same object again the next time a call is made. Is this possible?

It seems to be a conscious design decision that the apache environment is not visible within the service calls. Is there a way to get to the request_rec or server_rec objects created by apache, from within the service?


Thanks,
Shaun
------=_Part_119892_7292091.1185449556319--