Details
-
Bug
-
Status: Resolved
-
Critical
-
Resolution: Fixed
-
1.4
-
None
-
None
Description
Rampart throws an Exception. A SOAP-Fault is generated and will be send to the caller. This SOAP-Fault is also Processed by Rampart and while processing this Fault Message, Rampart throws another Error that causes Axis2 to send an HTML-internal error message to the caller.
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Header xmlns:wsa="http://www.w3.org/2005/08/addressing"><wsa:Action>XXXXXXXXX/Fault/FaultName</wsa:Action><wsa:RelatesTo>urn:uuid:E4331B281C8C1BE1411210178240805</wsa:RelatesTo></soapenv:Header><soapenv:Body><soapenv:Fault xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"><faultcode>wsse:InvalidSecurity</faultcode><faultstring>Cannot load password callback class: xxx.xxx.xxx.PWCBHandler.java</faultstring><detail /></soapenv:Fault></soapenv:Body></soapenv:Envelope>
2008-01-31 23:37:05,844 [http-8080-Processor15] DEBUG org.apache.axis2.engine.Phase - [MessageContext: logID=urn:uuid:AEE3166C73B98914F81201818949494] Invoking Handler 'Apache Rampart outflow handler' in Phase 'Security'
org.apache.ws.security.WSSecurityException: Error in converting SOAP Envelope to Document; nested exception is:
org.apache.axiom.soap.SOAPProcessingException: Only Characters are allowed here
in Axis2Util.getDocumentFromSOAPEnveloper
This Exception does not make the way through Axis engine..... somehow the following exception pops up at Axis2Servlet
"org.apache.axis2.AxisFault: Error in extracting message properties"
Attachments
Issue Links
- is blocked by
-
AXIOM-113 Error in serializing SOAP 1.1 SOAP Faults
- Closed