cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jiang Ning <ning.ji...@iona.com>
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/...
Date Mon, 25 Sep 2006 02:52:10 GMT
Hi Dan,

Transport may use message context to talk with the Application code. And 
the JAX-WS front end to provide 
BindingProvider.get{Request|Response}Context() API for the request & 
response context setup. The original Client side API only provide 
Context paramenter for the method invoke, but how Client side can get 
the response message context. 
If we using the context for in&out message context copy for making no 
change with the rt endpoint Client API, I think it will make some 
confusedness because we mess up the request and response context.

Any suggestions are welcome.

Thanks,
Willem.

Dan Diephouse wrote:

> 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<String, Object> context);
>> +                    Map<String, Object> requestContext,
>> +                    Map<String, Object> responseContext);
>>  
>>      Endpoint getEndpoint();
>>       
>
>
>


-- 
Willem Jiang
Software Engineer

IONA Asia Pacific Software Development Center
2/F, Unit A, Information Center
Zhongguancun Software Park Haidian District,
Beijing, P.R.China (100094)

Tel: +86-10-82825151 - 523
Fax: +86-10-82825210
Email: ning.jiang@iona.com



Mime
View raw message