From sandesha-dev-return-537-apmail-ws-sandesha-dev-archive=ws.apache.org@ws.apache.org Sun Jan 22 19:06:58 2006 Return-Path: Delivered-To: apmail-ws-sandesha-dev-archive@www.apache.org Received: (qmail 97923 invoked from network); 22 Jan 2006 19:06:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 22 Jan 2006 19:06:57 -0000 Received: (qmail 23472 invoked by uid 500); 22 Jan 2006 19:06:57 -0000 Delivered-To: apmail-ws-sandesha-dev-archive@ws.apache.org Received: (qmail 23225 invoked by uid 500); 22 Jan 2006 19:06:56 -0000 Mailing-List: contact sandesha-dev-help@ws.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list sandesha-dev@ws.apache.org Received: (qmail 23214 invoked by uid 99); 22 Jan 2006 19:06:56 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 22 Jan 2006 11:06:56 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of ssanka@gmail.com designates 66.249.82.202 as permitted sender) Received: from [66.249.82.202] (HELO xproxy.gmail.com) (66.249.82.202) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 22 Jan 2006 11:06:55 -0800 Received: by xproxy.gmail.com with SMTP id t15so530292wxc for ; Sun, 22 Jan 2006 11:06:34 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=mO0fTaOQho84rPewu7dA9hP2ZGNTgq0+N4S5EOPi+UD6yVT50oCLjt7oAuFaq1SxFQnAh9vEGeKj5iTGOUsMz5OF80Y9MsrgTvhDNr1lcpAK5nji357b3+xUL2l87ol8oWfHnA268HxdMtRNIjln8Hg/6PZCH0BU09zivfrN+ZQ= Received: by 10.70.103.13 with SMTP id a13mr4491478wxc; Sun, 22 Jan 2006 11:06:32 -0800 (PST) Received: by 10.70.109.7 with HTTP; Sun, 22 Jan 2006 11:06:32 -0800 (PST) Message-ID: <1e8c1ed40601221106m6f95126fs928b6afe46e444ec@mail.gmail.com> Date: Mon, 23 Jan 2006 01:06:32 +0600 From: Sanka Samaranayake To: Benjamin Schmeling Subject: Re: WS Commons Policy Cc: Jaliya Ekanayake , sandesha-dev@ws.apache.org In-Reply-To: <43D3CBE2.70002@gmx.de> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <43D0FC9D.1030203@gmx.de> <00c401c61ea9$9bcbf860$c0039f95@ads.iu.edu> <43D3CBE2.70002@gmx.de> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Hi Benjamin, On 1/23/06, Benjamin Schmeling wrote: > Okay, but I could use the Ws Commons Policy implementation to intersect > the policies of the server and the client (Assuming I know how to > retrieve them). I tried it out with examples of RM-Policy, but the > results of the intersection is not as I expected: > > Policy A is: > > xmlns:wsdl=3D"http://schemas.xmlsoap.org/wsdl/" > xmlns:wsp=3D"http://schemas.xmlsoap.org/ws/2004/09/policy" > > xmlns:wsrm=3D"http://schemas.xmlsoap.org/ws/2005/02/rm/policy" > xmlns:wsu=3D"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wsse= curity-utility-1.0.xsd" > wsu:Id=3D"MyPolicy"> > > > > > > > > > > Policy B is: > > xmlns:wsdl=3D"http://schemas.xmlsoap.org/wsdl/" > xmlns:wsp=3D"http://schemas.xmlsoap.org/ws/2004/09/policy" > > xmlns:wsrm=3D"http://schemas.xmlsoap.org/ws/2005/02/rm/policy" > xmlns:wsu=3D"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wsse= curity-utility-1.0.xsd" > wsu:Id=3D"MyPolicy"> > > > > > > > > > > The intersection is: > > wsu:Id=3D"MyPolicy"> > > > xmlns:wsrm=3D"http://schemas.xmlsoap.org/ws/2005/02/rm/policy"> > > > Milliseconds=3D"200" /> > > xmlns:wsrm=3D"http://schemas.xmlsoap.org/ws/2005/02/rm/policy"> > > > > > > > > > > I expected, that there is no common agreement between client and server, > because of the different InactivityTimeout. Is that because of the > general definition of WS-Policy ? yes, thats the exact definition of policy intersect according WS-Policy specification. The result you got is correct according to the sepc. > Do we need another implementation for > the concrete domain specific policy assertions (e.g. RMPolicy)? Rather you need a domain specific policy processor (say RMPolicyProcessor) to evaluate those two RMAssertions and to throw a fault saying that there is a policy violation or policy incompatibility . Sanka > > Thanks, > > Benjamin > > > Hi Benjamin, > > > > Sandesha 1 works with Axis 1 and it supports only the static policy. > > That is policy is read from a file in both client and server side. > > WS-Commons policy will be used in Axis2 and Sandesha2 to get the > > policies dynamically from server. Still the client side of Axis2 needs > > some work regarding dynamic policies. > > It will be there soon. > > > > Thanks, > > Jaliya > > > > > > > > ----- Original Message ----- From: "Benjamin Schmeling" > > > > To: > > Sent: Friday, January 20, 2006 10:07 AM > > Subject: WS Commons Policy > > > > > >> Hi, > >> > >> I am using Apache Sandesha 1.0 and Axis for reliable messaging. Now I > >> want > >> to attach a policy to my web service, so the client can get the > >> policy of > >> that web service (which should only accept reliable messaging calls) a= nd > >> check if the clients policy is supported by this service. I am using > >> Axis > >> 1.2.1. > >> > >> Is there any possibility to do this with WS Commons Policy ? I saw tha= t > >> there are provided a policy model and merging, normalizing operations.= I > >> don't know how to get the policy from the server and if it is > >> possible to > >> do this with Axis 1.x. > >> > >> Thanks, > >> > >> Benjamin > >> > >> > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org > For additional commands, e-mail: sandesha-dev-help@ws.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org For additional commands, e-mail: sandesha-dev-help@ws.apache.org