Wso2 Fault Sequence Error Handling Header
I am currently developing an API that will send a request to the Endpoint and will response back to the client.
On my fault sequence, I will log the error code and error message by using the makefault mediator. Everything is working fine about the error code and message logging. It just that, the HTTP header return as 500 (Internal Server Error) for every error.
This is my Fault Sequence look like.
<faultSequence>
<makefault description="" version="soap11">
<code value="soap11Env:VersionMismatch" xmlns:soap11Env="http://schemas.xmlsoap.org/soap/envelope/"/>
<reason expression="get-property('ERROR_CODE')"/>
<role/>
<detail/>
</makefault>
<log level="custom">
<property expression="get-property('HTTP_SC')" name="header"/>
</log>
<header name="To" action="remove"/>
<property name="RESPONSE" value="true"/>
I try to catch the HTTP code inside the message context. The value is null
LogMediator header = null
But when the response is being send back to the client, it return the HTTP as 500(Interal Server Error)
Any advice would help here. Kindly assist. Thank you StackOverFlow.
wso2 wso2ei synapse
asked Nov 27 '18 at 9:09
ameruddin jamilameruddin jamil
2319
add a comment |
I am currently developing an API that will send a request to the Endpoint and will response back to the client.
On my fault sequence, I will log the error code and error message by using the makefault mediator. Everything is working fine about the error code and message logging. It just that, the HTTP header return as 500 (Internal Server Error) for every error.
This is my Fault Sequence look like.
<faultSequence>
<makefault description="" version="soap11">
<code value="soap11Env:VersionMismatch" xmlns:soap11Env="http://schemas.xmlsoap.org/soap/envelope/"/>
<reason expression="get-property('ERROR_CODE')"/>
<role/>
<detail/>
</makefault>
<log level="custom">
<property expression="get-property('HTTP_SC')" name="header"/>
</log>
<header name="To" action="remove"/>
<property name="RESPONSE" value="true"/>
I try to catch the HTTP code inside the message context. The value is null
LogMediator header = null
But when the response is being send back to the client, it return the HTTP as 500(Interal Server Error)
Any advice would help here. Kindly assist. Thank you StackOverFlow.
wso2 wso2ei synapse
asked Nov 27 '18 at 9:09
ameruddin jamilameruddin jamil
2319
Not sure, but I guess it might be related to the scope. Can you try <property xmlns:ns="org.apache.synapse/xsd" name="Status" expression="$axis2:HTTP_SC"/> or get-property('axis2', 'HTTP_SC') or get-property('transport', 'HTTP_SC') to see if it works
– Martin Hald
Dec 3 '18 at 8:58
add a comment |
I am currently developing an API that will send a request to the Endpoint and will response back to the client.
On my fault sequence, I will log the error code and error message by using the makefault mediator. Everything is working fine about the error code and message logging. It just that, the HTTP header return as 500 (Internal Server Error) for every error.
This is my Fault Sequence look like.
<faultSequence>
<makefault description="" version="soap11">
<code value="soap11Env:VersionMismatch" xmlns:soap11Env="http://schemas.xmlsoap.org/soap/envelope/"/>
<reason expression="get-property('ERROR_CODE')"/>
<role/>
<detail/>
</makefault>
<log level="custom">
<property expression="get-property('HTTP_SC')" name="header"/>
</log>
<header name="To" action="remove"/>
<property name="RESPONSE" value="true"/>
I try to catch the HTTP code inside the message context. The value is null
LogMediator header = null
But when the response is being send back to the client, it return the HTTP as 500(Interal Server Error)
Any advice would help here. Kindly assist. Thank you StackOverFlow.
wso2 wso2ei synapse
asked Nov 27 '18 at 9:09
ameruddin jamilameruddin jamil
2319
I am currently developing an API that will send a request to the Endpoint and will response back to the client.
On my fault sequence, I will log the error code and error message by using the makefault mediator. Everything is working fine about the error code and message logging. It just that, the HTTP header return as 500 (Internal Server Error) for every error.
This is my Fault Sequence look like.
<faultSequence>
<makefault description="" version="soap11">
<code value="soap11Env:VersionMismatch" xmlns:soap11Env="http://schemas.xmlsoap.org/soap/envelope/"/>
<reason expression="get-property('ERROR_CODE')"/>
<role/>
<detail/>
</makefault>
<log level="custom">
<property expression="get-property('HTTP_SC')" name="header"/>
</log>
<header name="To" action="remove"/>
<property name="RESPONSE" value="true"/>
I try to catch the HTTP code inside the message context. The value is null
LogMediator header = null
But when the response is being send back to the client, it return the HTTP as 500(Interal Server Error)
Any advice would help here. Kindly assist. Thank you StackOverFlow.
wso2 wso2ei synapse
wso2 wso2ei synapse
asked Nov 27 '18 at 9:09
ameruddin jamilameruddin jamil
2319
asked Nov 27 '18 at 9:09
ameruddin jamilameruddin jamil
2319
asked Nov 27 '18 at 9:09
ameruddin jamilameruddin jamil
2319
asked Nov 27 '18 at 9:09
ameruddin jamilameruddin jamil
2319
asked Nov 27 '18 at 9:09
ameruddin jamilameruddin jamil
2319
2319
Not sure, but I guess it might be related to the scope. Can you try <property xmlns:ns="org.apache.synapse/xsd" name="Status" expression="$axis2:HTTP_SC"/> or get-property('axis2', 'HTTP_SC') or get-property('transport', 'HTTP_SC') to see if it works
– Martin Hald
Dec 3 '18 at 8:58
add a comment |
Not sure, but I guess it might be related to the scope. Can you try <property xmlns:ns="org.apache.synapse/xsd" name="Status" expression="$axis2:HTTP_SC"/> or get-property('axis2', 'HTTP_SC') or get-property('transport', 'HTTP_SC') to see if it works
– Martin Hald
Dec 3 '18 at 8:58
Not sure, but I guess it might be related to the scope. Can you try <property xmlns:ns="org.apache.synapse/xsd" name="Status" expression="$axis2:HTTP_SC"/> or get-property('axis2', 'HTTP_SC') or get-property('transport', 'HTTP_SC') to see if it works
– Martin Hald
Dec 3 '18 at 8:58
Not sure, but I guess it might be related to the scope. Can you try <property xmlns:ns="org.apache.synapse/xsd" name="Status" expression="$axis2:HTTP_SC"/> or get-property('axis2', 'HTTP_SC') or get-property('transport', 'HTTP_SC') to see if it works
– Martin Hald
Dec 3 '18 at 8:58
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53496112%2fwso2-fault-sequence-error-handling-header%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53496112%2fwso2-fault-sequence-error-handling-header%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Not sure, but I guess it might be related to the scope. Can you try <property xmlns:ns="org.apache.synapse/xsd" name="Status" expression="$axis2:HTTP_SC"/> or get-property('axis2', 'HTTP_SC') or get-property('transport', 'HTTP_SC') to see if it works
– Martin Hald
Dec 3 '18 at 8:58