Return-Path: Delivered-To: apmail-ws-axis-user-archive@www.apache.org Received: (qmail 64068 invoked from network); 8 Oct 2008 12:40:12 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 8 Oct 2008 12:40:12 -0000 Received: (qmail 23523 invoked by uid 500); 8 Oct 2008 12:40:05 -0000 Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 22532 invoked by uid 500); 8 Oct 2008 12:40:03 -0000 Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-user@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-user@ws.apache.org Received: (qmail 22521 invoked by uid 99); 8 Oct 2008 12:40:03 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Oct 2008 05:40:03 -0700 X-ASF-Spam-Status: No, hits=2.1 required=10.0 tests=DNS_FROM_SECURITYSAGE,HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of nandana.cse@gmail.com designates 209.85.200.172 as permitted sender) Received: from [209.85.200.172] (HELO wf-out-1314.google.com) (209.85.200.172) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Oct 2008 12:38:58 +0000 Received: by wf-out-1314.google.com with SMTP id 25so3953645wfc.28 for ; Wed, 08 Oct 2008 05:39:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type:references; bh=dfQn/72i0rl/uT06XtHJAcIkhcCbA84+WHebFv9y73s=; b=berpjfa3MZD4NEJrhM+tZNMyGxt7617yq+621i9aSAnrGJFZJ4Nhq85MfDcyXfsj3Z 3GHH6qvL14u6AmZ4H6jqk+XeR4YjZ8HH8HAUbRSXrZSws4EMaNy/PXHwNifWjtKVmmgW mBxm2iHgjV8/hG8N0/h4mKTY6l2ewK3SlVK+E= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:references; b=K/OcowgYMvNDcs72Ic2KZBDFM9OLV0VGyvXsgYLM9l6OjL2ZIYLji+DY7K0ePexIX/ olWBgfp8XS865/ydnFuYPhrer/+/WoRs5vSqHLSAZ9JYQH8hBo9ivMYDT6e2CcNJx3/+ aWzLWlHPH3r4K7tRqNjazb8R2BdqqQlEjYlh4= Received: by 10.142.188.4 with SMTP id l4mr3399811wff.151.1223469573820; Wed, 08 Oct 2008 05:39:33 -0700 (PDT) Received: by 10.142.153.13 with HTTP; Wed, 8 Oct 2008 05:39:33 -0700 (PDT) Message-ID: <9e2fff830810080539x2103637cp5525cfef165df172@mail.gmail.com> Date: Wed, 8 Oct 2008 18:09:33 +0530 From: "Nandana Mihindukulasooriya" To: mrthompson@lbl.gov, axis-user@ws.apache.org Subject: Re: Problem attaching ws-policy at message level In-Reply-To: <48EC651E.40905@lbl.gov> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_76783_7884630.1223469573812" References: <48EC0681.6090001@lbl.gov> <9e2fff830810072139l426a1235h53168c9210f17cfe@mail.gmail.com> <48EC651E.40905@lbl.gov> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_76783_7884630.1223469573812 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi Mary, How did you create the SimpleServiceStub? It says it was auto-generated from > WSDL, but you did not include a WSDL in the example. Does the wsdl2java > included in axis 1.4.1 work out of the box or does it need to become > "rampart aware" in some way? > No, you don't need to make wsdl2java rampart aware. In the above scenario I used the code first approach. I just created a the service archive with the necessary classes and the services.xml. WSDL was generated by Axis2. Then I created stubs using axis2 codegen tool by pointing it the WSDL generated by Axis2 engine. thanks, nandana Nandana Mihindukulasooriya wrote: > >> Hi Mary, >> >> Has anyone had success in attaching ws-policy at the message level >> in the xml.services file? I am trying to get the request messages >> signed and time stamped and the response messages just time stamped. >> >> >> I just tested this scenario with Axis2 1.4.1 and Rampart nightly build and >> worked as expected for me. I have attached the service [1] that I tested for >> your reference. I also included the SOAP messages for each of the scenarios >> I have tested. However in the response also, time stamp will be signed. >> >> I have followed Nandana's tutorial at https://wso2.org/library/3786 >> and used the following PolicyAttachement element >> The service seems to just ignore the signedParts. E.g when I send it >> a non-signed body it does not reject the message. Just to see what >> was happening, I tried attaching the policy to the response message >> and it did not sign the response. >> >> >> When you attach the policies as you have described above using the >> services.xml, do they appear on the generated WSDL ? >> >> thanks, >> nandana >> >> [1] - >> https://wso2.org/repos/wso2/people/nandana/demo-service/demo-service.zip >> >> -- >> Nandana Mihindukulasooriya WSO2 inc. >> >> http://nandana83.blogspot.com/ >> http://www.wso2.org >> > > -- Nandana Mihindukulasooriya WSO2 inc. http://nandana83.blogspot.com/ http://www.wso2.org ------=_Part_76783_7884630.1223469573812 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline
Hi Mary,

How did you create the SimpleServiceStub? It says it was auto-generated from WSDL, but you did not include a WSDL in the example. Does the wsdl2java included in axis 1.4.1 work out of the box or does it need to become "rampart aware" in some way?

No, you don't need to make wsdl2java rampart aware. In the above scenario I used the code first approach. I just created a the service archive with the necessary classes and the services.xml. WSDL was generated by Axis2.  Then I created stubs using axis2 codegen tool by pointing it the WSDL generated by Axis2 engine.

thanks,
nandana


Nandana Mihindukulasooriya wrote:
Hi Mary,

   Has anyone had success in attaching ws-policy at the message level
   in the xml.services file? I am trying to get the request  messages
   signed and time stamped and the response messages just time stamped.


I just tested this scenario with Axis2 1.4.1 and Rampart nightly build and worked as expected for me. I have attached the service [1] that I tested for your reference. I also included the SOAP messages for each of the scenarios I have tested. However in the response also, time stamp will be signed.
 
   I have followed Nandana's tutorial at https://wso2.org/library/3786
   and used the following PolicyAttachement element
   The service seems to just ignore the signedParts. E.g when I send it
   a non-signed body it does not reject the message. Just to see what
   was happening, I tried attaching the policy to the response message
   and it did not sign the response.


When you attach the policies as you have described above using the services.xml, do they appear on the generated WSDL ?

thanks,
nandana

[1] - https://wso2.org/repos/wso2/people/nandana/demo-service/demo-service.zip

--
Nandana Mihindukulasooriya  WSO2 inc.

http://nandana83.blogspot.com/
http://www.wso2.org




--
Nandana Mihindukulasooriya  
WSO2 inc.

http://nandana83.blogspot.com/
http://www.wso2.org
------=_Part_76783_7884630.1223469573812--