You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by "Ruwan Linton (JIRA)" <ji...@apache.org> on 2007/10/23 15:19:50 UTC
[jira] Created: (SYNAPSE-157) Unexpected exception when sending a
SOAPFault on soap12
Unexpected exception when sending a SOAPFault on soap12
-------------------------------------------------------
Key: SYNAPSE-157
URL: https://issues.apache.org/jira/browse/SYNAPSE-157
Project: Synapse
Issue Type: Bug
Components: Core
Affects Versions: 1.1.QA.B.2
Environment: Java-15 on Unix
Reporter: Ruwan Linton
Assignee: Ruwan Linton
Priority: Critical
Fix For: 1.1.-RC1-B1
If you try to create a fault using the makefault and specifying the soap version to be soap12 Rampart throws and unexpected exception of invlid soap fault.
See the following thread for the configurations and the stack trace;
http://www.nabble.com/Access-to-validation-error-message-tf4498668.html#a13284520
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-dev-help@ws.apache.org
[jira] Issue Comment Edited: (SYNAPSE-157) Unexpected exception
when sending a SOAPFault on soap12
Posted by "Ruwan Linton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537195 ]
ruwan edited comment on SYNAPSE-157 at 10/23/07 8:27 PM:
----------------------------------------------------------------
Fixed in the revision r587763.
Here is an explanation to the issue.
This issue exists only when security is engaged for a SOAP12 Fault going out with a blank Detail element in the Fault. The issue is after going the message in to rampart it tries to build the message and fails from AXIOM builder saying that wrong element order, even though the message contains the nodes correctly, the blank Detail element appears before code and reason elements and hence AXIOM throws this Exception.
As a work around I have removed the Detail element from the Fault if it is blank because the Detail element is optional in the SOAP12 spec. If there is some data in the Detail node (that is, if it is not blank) this problem is not encountered, do if you put detail in to the detail node it will be sent where as if you haven't it wont send a Detail element (Even if you put a blank Detail in to the Fault, the resulting envelope that the client is getting does not contain a Detail element because it is blank, so I think this is a solid work around)
was (Author: ruwan):
Fixed in the revision r587763.
Here is an explanation to the issue.
This issue exists only when security is engaged for a SOAP12 Fault going out with a blank Detail element in the Fault. The issue is after going the message in to rampart it tries to build the message and fails from AXIOM builder saying that wrong element order, even though the message contains the nodes correctly, the blank Detail element appears before code and reason elements and hence AXIOM throws this Exception.
As a work around I have removed the Detail element from the Fault if it is blank because the Detail element is option in the SOAP12 spec. If there is some data in the Detail node (that is, if it is not blank) this problem is not encountered, do if you put detail in to the detail node it will be sent where as if you haven't it wont send a Detail element (Even if you put a blank Detail in to the Fault, the resulting envelope that the client is getting does not contain a Detail element because it is blank, so I think this is a solid work around)
> Unexpected exception when sending a SOAPFault on soap12
> -------------------------------------------------------
>
> Key: SYNAPSE-157
> URL: https://issues.apache.org/jira/browse/SYNAPSE-157
> Project: Synapse
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.1.QA.B.2
> Environment: Java-15 on Unix
> Reporter: Ruwan Linton
> Assignee: Ruwan Linton
> Priority: Critical
> Fix For: 1.1.-RC1-B1
>
>
> If you try to create a fault using the makefault and specifying the soap version to be soap12 Rampart throws and unexpected exception of invlid soap fault.
> See the following thread for the configurations and the stack trace;
> http://www.nabble.com/Access-to-validation-error-message-tf4498668.html#a13284520
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-dev-help@ws.apache.org
[jira] Resolved: (SYNAPSE-157) Unexpected exception when sending a
SOAPFault on soap12
Posted by "Ruwan Linton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ruwan Linton resolved SYNAPSE-157.
----------------------------------
Resolution: Fixed
Fixed in the revision r587763.
Here is an explanation to the issue.
This issue exists only when security is engaged for a SOAP12 Fault going out with a blank Detail element in the Fault. The issue is after going the message in to rampart it tries to build the message and fails from AXIOM builder saying that wrong element order, even though the message contains the nodes correctly, the blank Detail element appears before code and reason elements and hence AXIOM throws this Exception.
As a work around I have removed the Detail element from the Fault if it is blank because the Detail element is option in the SOAP12 spec. If there is some data in the Detail node (that is, if it is not blank) this problem is not encountered, do if you put detail in to the detail node it will be sent where as if you haven't it wont send a Detail element (Even if you put a blank Detail in to the Fault, the resulting envelope that the client is getting does not contain a Detail element because it is blank, so I think this is a solid work around)
> Unexpected exception when sending a SOAPFault on soap12
> -------------------------------------------------------
>
> Key: SYNAPSE-157
> URL: https://issues.apache.org/jira/browse/SYNAPSE-157
> Project: Synapse
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.1.QA.B.2
> Environment: Java-15 on Unix
> Reporter: Ruwan Linton
> Assignee: Ruwan Linton
> Priority: Critical
> Fix For: 1.1.-RC1-B1
>
>
> If you try to create a fault using the makefault and specifying the soap version to be soap12 Rampart throws and unexpected exception of invlid soap fault.
> See the following thread for the configurations and the stack trace;
> http://www.nabble.com/Access-to-validation-error-message-tf4498668.html#a13284520
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-dev-help@ws.apache.org