axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nandana Mihindukulasooriya" <>
Subject Re: Problem attaching ws-policy at message level
Date Wed, 08 Oct 2008 12:39:33 GMT
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.


Nandana Mihindukulasooriya wrote:
>> Hi Mary,
>>    Has anyone had success in attaching ws-policy at the message level
>>    in the 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
>>    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] -
>> --
>> Nandana Mihindukulasooriya  WSO2 inc.

Nandana Mihindukulasooriya
WSO2 inc.

View raw message