2012/4/4 Philippe A.
> I still wish I could avoid policy duplication on the client side. Ideally
> I would like to write a rampart.xml with no policy inside and assign that
> config to my generated service client.
>
>
I went a step further and gave up using wsdl2java. Writing an Axis client
by h
2012/4/4 Philippe A.
>
> http://ws.apache.org/rampart/policy";>
> ...
>
> client.PWCBHandler
> ...
> ...
>
> provider="org.apache.ws.security.components.crypto.Merlin">
>name="org.apache.ws.security.crypto.merlin.keystore.type">JKS
>name="org.apache.ws.security.crypt
2012/2/1 COURTAULT Francois
> In fact the simple question I have is: Is there any sample/tutorial
> available somewhere in order to have a client code which doesn’t need to
> have an external policy file available at the client side as we already
> have it in the stub generated and which works
alto.test.axis2.TestSimpleWSAxis2ClientX509.main(TestSimpleWSAxis2ClientX509.java:50)
Any idea ?
Best Regards.
From: James Annesley [mailto:james.annes...@infoshare-is.com]
Sent: mardi 31 janvier 2012 21:10
To: java-user@axis.apache.org
Subject: RE: Completly lost
Hi Francois,
I noticed you
Hi Francois,
I noticed you don't need the server policy file at all on the client side.
I do this:
client.engageModule("rampart");
options.setProperty(RampartMessageData.KEY_RAMPART_POLICY, null);
where client is the ServiceClient.
HTH
James
From: COURTAULT Francois [ma
