I solve the problem:
1) On same axis2 installation I install rampart 1.3 and then rampart
1.4(conflict wss4j-1.5.X)
I take clean installation of axis2 and rampart 1.4
2) And there was also problem with my JCE(no such algorithm):
2.1) Install Unlimited strength Jurisdiction Policy
I want it to return an XML that shows the SOAP Fault returned, so the client
understand, how can I achieve this?
I have situation:
java 1.6_10
Tomcat 6.0.18
axis2_1_4
rampart 1.4
Client send soap message with wrong signed key and rampart return the response
is html, more precisely I get
Hi,
Anybody have a solution to this problem. I really would like to avoid coding
changes since I am upgrading my app from axis 1.2.x to axis2. Just to prove
my issue when I changed one call to return a string it started working fine.
I would really appreciate any help.
Thanks
Sanjay
Adding a handler may not work. What if the request has passed that
handler and soon after that the service is undeployed?
Azeez
On Fri, Feb 13, 2009 at 2:26 AM, Yan Liu cigi_yan...@yahoo.com wrote:
So what if we put a handler there to disable all requests for the service
being removed (or
