If this helps in terms of what to do and to sort things out:
1. If possible, use TCP/IP monitor in your
IDE.
If not, GOOGLE to use external
SOAP UI and TCPMon to capture the outbound SOAP request and the inbound SOAP response
This exercise is to validate the factual error that the SOAP request did not send the wsse:Security header to the Web service provider
which expect it (as part of the Message Level security).
Again, for the Message Level security,
you should know it if Web service provider expects it or not.
If not, just check or ask the provider documentation.
And what is included in wsse:Security header? what type of security needed? questions like these must be asked
and answer before you can implement portion of wsse:Security header to satisfy the web service provider's security expectation.
2. How can you add wsse:Security header to the outbound SOAP request?
By Implementing the SOAP Message Handler (or Interceptor) Check AXIS2 for handler class naming aspect.
Simplified flow-wise:
Your code/Proxy client
----> SOAP Message Handler (to be implemented progammatically to add wsse:Security header to
the outbound SOAP request using rampart api. This is the challenging part. So good luck.)
----> SOAP request completed with wsse:Security header
----> Web service provider.
Check AXIS2 website for flow and/or rampart api. If you GOOGLE for the term like wsse:Security and SOAP Message handler,
you will see things more clear in case you need more direction and/or code sample using specific AXIS2.