Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 31080 invoked from network); 7 Dec 2006 16:16:46 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 7 Dec 2006 16:16:46 -0000 Received: (qmail 37757 invoked by uid 500); 7 Dec 2006 16:16:50 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 37718 invoked by uid 500); 7 Dec 2006 16:16:50 -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: List-Id: Delivered-To: mailing list axis-dev@ws.apache.org Received: (qmail 37707 invoked by uid 99); 7 Dec 2006 16:16:50 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Dec 2006 08:16:50 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Dec 2006 08:16:41 -0800 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 9096C7142F8 for ; Thu, 7 Dec 2006 08:16:21 -0800 (PST) Message-ID: <11698840.1165508181589.JavaMail.jira@brutus> Date: Thu, 7 Dec 2006 08:16:21 -0800 (PST) From: "Shaoguang Cong (JIRA)" To: axis-dev@ws.apache.org Subject: [jira] Commented: (AXIS2-1823) Client API needs a method to access Current Message Context In-Reply-To: <23689705.1165266080987.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ http://issues.apache.org/jira/browse/AXIS2-1823?page=comments#action_12456470 ] Shaoguang Cong commented on AXIS2-1823: --------------------------------------- Glen, I'm playing with the released version 2.1.1. So I cannot check the fix in the trunk. >From purely a user's view, I'll echo Sanjiva's comment on avoiding to use some methods not so obvious to the app developer. Could just add the method as Deepal suggested, like ServiceClient.getCurrentOperationContext(); Or even ServiceClient.getCurrentMessageContext(). It's the returned MessageContext really matter in most cases if not all of the cases(e.g. retrieve soap header info). > Client API needs a method to access Current Message Context > ----------------------------------------------------------- > > Key: AXIS2-1823 > URL: http://issues.apache.org/jira/browse/AXIS2-1823 > Project: Apache Axis 2.0 (Axis2) > Issue Type: New Feature > Components: client-api > Reporter: Shaoguang Cong > Assigned To: Glen Daniels > > The generated client stub doesn't have a way to access MessageContext or SOAPHeader. Client would like to access the header upon returned from the service. It's ideal to add a getter method in the client stub or Service Client class. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org For additional commands, e-mail: axis-dev-help@ws.apache.org