You are viewing a plain text version of this content. The canonical link for it is here.
Posted to rampart-dev@ws.apache.org by "chris grzegorczyk (JIRA)" <ji...@apache.org> on 2008/06/23 17:38:45 UTC
[jira] Commented: (RAMPART-164) Error while processing SOAP-Fault
(Axis2Util.getDocumentFromSOAPEnveloper) -> Axis2 HTML Error Page
[ https://issues.apache.org/jira/browse/RAMPART-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12607264#action_12607264 ]
chris grzegorczyk commented on RAMPART-164:
-------------------------------------------
Hi Folks,
I've been following this problem for a little while now. Has there been any change in the situation? I notice that the AXIOM bug is as yet unassigned -- is that a sign the issue will not be addressed?
Is there possibly a short-term work around?
Using SOAP 1.2 is not an option for me.
thanks in advance.
> Error while processing SOAP-Fault (Axis2Util.getDocumentFromSOAPEnveloper) -> Axis2 HTML Error Page
> ----------------------------------------------------------------------------------------------------
>
> Key: RAMPART-164
> URL: https://issues.apache.org/jira/browse/RAMPART-164
> Project: Rampart
> Issue Type: Bug
> Components: rampart-core
> Affects Versions: 1.4
> Reporter: Stefan Lischke
> Assignee: Ruchith Udayanga Fernando
> Priority: Critical
>
> 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"
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Commented: (RAMPART-164) Error while processing SOAP-Fault
(Axis2Util.getDocumentFromSOAPEnveloper) -> Axis2 HTML Error Page
Posted by Stefan Lischke <li...@googlemail.com>.
i commented on the ws-commons bug, i hope someone will read it!
stefan
chris grzegorczyk (JIRA) wrote:
> [ https://issues.apache.org/jira/browse/RAMPART-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12607264#action_12607264 ]
>
> chris grzegorczyk commented on RAMPART-164:
> -------------------------------------------
>
> Hi Folks,
>
> I've been following this problem for a little while now. Has there been any change in the situation? I notice that the AXIOM bug is as yet unassigned -- is that a sign the issue will not be addressed?
>
> Is there possibly a short-term work around?
>
> Using SOAP 1.2 is not an option for me.
>
> thanks in advance.