No, you generally do not need to alter the axis2.xml file (assuming you're talking about the server-side axis2.xml file).
You will need to adapt the client-side configuration file, which sometimes is also called axis2.xml or client.axis2.xml, so that it includes a similar section about InflowSecurity and OutflowSecurity. Do you have that? If so, post it here; if not, there's your problem.
Hmmm so I guess that we figured out what my problem is... I don't have this axis2.xml file, and I'm not sure where to place it. I thought I would only need the server.xml to do the encryption. Should place this axis2.xml in META-INF directory inside my .aar file?
Joined: Mar 22, 2005
No. The META-INF/services.xml file is already in the .aar file, and it determines what security will be done on the *server*.
The file I'm talking about is used on the *client*. The security for both sides needs to match, or you'll get a mismatch error.
You'd use the client-side file name as value for the "axis2.xml" property that you pass to the client. (That's assuming that you're using Axis2 on the client side as well. If you're using some other client SOAP framework, then you need to consult its documentation for how to set its security options.)
Joined: Jan 22, 2009
Thank you so much,
I built my axis2.xml file and everything seemed to go well until I got another problem... I've been trying in any ways to make this work but seems that I'm not giving the right path of my client.properties file or something like this.