Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Received-SPF: neutral (herse.apache.org: local policy)
Message-ID: <467F102E.3000000@opensource.lk>
Date: Mon, 25 Jun 2007 06:15:34 +0530
From: Sanjiva Weerawarana <sanjiva@opensource.lk>
Organization: WSO2 Inc.
User-Agent: Thunderbird 1.5.0.12 (X11/20070604)
MIME-Version: 1.0
To: axis-dev@ws.apache.org
Subject: Re: [Axis2] Accessing properties set in options of the service client
References: <559c463d0706240059n1d333669yf1482480a10eca88@mail.gmail.com>
 <467EFFCB.2030006@opensource.lk>
In-Reply-To: <467EFFCB.2030006@opensource.lk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

+1. I don't think its at all correct to blindly copy all properties from 
in to out (or out to in). That's what the message receiver (or operation 
client, in Ruchith's case) must do for what it wants to copy. If the user 
explicitly wants to share stuff either they have to set it on the message 
context and explicitly get it from it or set it directly on the operation 
context and share it across all message contexts in that interaction.

Sanjiva.

Eran Chinthaka wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> This is a delicate issue, IIUC. We do copy some properties from request
> path to the response path, but not all. And also I don;t think we are
> copying all the properties to response properties. BTW, do we need to do
> that?
> Isn't it that you should set your properties to OperationContext if you
> want to get them in the response path? See for example, if I set the
> property addressingProcessed=true (a hypothetical property) to message
> context in the request path, it will be a disaster if you copy this
> property to out message context.
> 
> So I think current behavior is correct.
> 
> Chinthaka
> 
> Ruchith Fernando wrote:
>> Hi Devs,
>>
>> Some of the Rampart tests are failing due the properties set in the
>> options object of the ServiceClient are not available in the inflow to
>> be accessed by a handler (out-in operation). The properties are
>> available in only the outflow.
>>
>> Is this behavior correct?
>>
>> Thanks,
>> Ruchith
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-dev-help@ws.apache.org
>>
>>
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.3 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> 
> iD8DBQFGfv/LjON2uBzUhh8RAh1hAJ0YCrqYQJwPOPTXZYLROo27kwTS+QCcCaZw
> L+DgcCaFW9rRnfz9UCiTv3c=
> =eK+0
> -----END PGP SIGNATURE-----
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
> 
> 

-- 
Sanjiva Weerawarana, Ph.D.
Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
Director; Open Source Initiative; http://www.opensource.org/
Member; Apache Software Foundation; http://www.apache.org/
Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org