Return-Path: Delivered-To: apmail-incubator-cxf-dev-archive@locus.apache.org Received: (qmail 22222 invoked from network); 24 Sep 2006 18:47:27 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 24 Sep 2006 18:47:27 -0000 Received: (qmail 48539 invoked by uid 500); 24 Sep 2006 18:47:26 -0000 Delivered-To: apmail-incubator-cxf-dev-archive@incubator.apache.org Received: (qmail 48397 invoked by uid 500); 24 Sep 2006 18:47:26 -0000 Mailing-List: contact cxf-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cxf-dev@incubator.apache.org Delivered-To: mailing list cxf-dev@incubator.apache.org Received: (qmail 48385 invoked by uid 99); 24 Sep 2006 18:47:25 -0000 Received: from idunn.apache.osuosl.org (HELO idunn.apache.osuosl.org) (140.211.166.84) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 24 Sep 2006 11:47:25 -0700 Authentication-Results: idunn.apache.osuosl.org smtp.mail=dan@envoisolutions.com; spf=permerror X-ASF-Spam-Status: No, hits=0.0 required=5.0 tests= Received-SPF: error (idunn.apache.osuosl.org: domain envoisolutions.com from 204.127.225.93 cause and error) Received: from [204.127.225.93] ([204.127.225.93:55700] helo=alnrmhc13.comcast.net) by idunn.apache.osuosl.org (ecelerity 2.1.1.8 r(12930)) with ESMTP id 9B/C1-11238-BB2D6154 for ; Sun, 24 Sep 2006 11:47:25 -0700 Received: from [192.168.3.100] (c-71-205-191-164.hsd1.mi.comcast.net[71.205.191.164]) by comcast.net (alnrmhc13) with ESMTP id <20060924184720b1300l8b85e>; Sun, 24 Sep 2006 18:47:21 +0000 Message-ID: <4516D293.7050903@envoisolutions.com> Date: Sun, 24 Sep 2006 14:46:43 -0400 From: Dan Diephouse User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: cxf-dev@incubator.apache.org CC: cxf-commits@incubator.apache.org Subject: Re: svn commit: r449188 - in /incubator/cxf/trunk: api/src/main/java/org/apache/cxf/endpoint/ rt/core/src/main/java/org/apache/cxf/endpoint/ rt/frontend/jaxws/src/main/java/org/apache/cxf/jaxws/ rt/frontend/jaxws/src/main/java/org/apache/cxf/jaxws/support/... References: <20060923065223.B306C1A981A@eris.apache.org> In-Reply-To: <20060923065223.B306C1A981A@eris.apache.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N I'm not very keen on adding a request & response context to the client api. I don't think it makes sense from an internal standpoint - it seems awfully tied to JAX-WS. Do we have to do this? Is there a way to do it where it doesn't pollute our API? - Dan ningjiang@apache.org wrote: > Modified: incubator/cxf/trunk/api/src/main/java/org/apache/cxf/endpoint/Client.java > URL: http://svn.apache.org/viewvc/incubator/cxf/trunk/api/src/main/java/org/apache/cxf/endpoint/Client.java?view=diff&rev=449188&r1=449187&r2=449188 > ============================================================================== > --- incubator/cxf/trunk/api/src/main/java/org/apache/cxf/endpoint/Client.java (original) > +++ incubator/cxf/trunk/api/src/main/java/org/apache/cxf/endpoint/Client.java Fri Sep 22 23:52:22 2006 > @@ -30,12 +30,14 @@ > * Invokes an operation syncronously > * @param oi The operation to be invoked > * @param params The params that matches the parts of the input message of the operation > - * @param context Optional (can be null) contextual information for the invocation > + * @param requestContext Optional (can be null) request contextual information for the invocation > + * @param responseContext Optional (can be null) response contextual information for the invocation > * @return The return values that matche the parts of the output message of the operation > */ > Object[] invoke(BindingOperationInfo oi, > Object[] params, > - Map context); > + Map requestContext, > + Map responseContext); > > Endpoint getEndpoint(); > > -- Dan Diephouse Envoi Solutions http://envoisolutions.com http://netzooid.com/blog