could not display ${out.body} at Log for external soap provider
I already got reply from to uri which is external soap service provider. but why I could not see the response in log with ${out.body} i think soap is InOut exchangepattern, it should have out.body always. My code example looks like below.
Any hints are more than welcome!
<from uri="cxf://http://localhost:8080/myservice?dataFormat=MESSAGE&wsdlURL=wsdl%2Fmyservice.wsdl" />
<to uri="http4://localhost:8888/mockservice"/>
<log message="##### After soap provider out.body ##### ${out.body}" loggingLevel="INFO" />`
apache-camel
edited Nov 24 '18 at 8:42
Francesco Montesano
5,5232651
asked Nov 21 '18 at 19:46
stewchickenstewchicken
7611
add a comment |
I already got reply from to uri which is external soap service provider. but why I could not see the response in log with ${out.body} i think soap is InOut exchangepattern, it should have out.body always. My code example looks like below.
Any hints are more than welcome!
<from uri="cxf://http://localhost:8080/myservice?dataFormat=MESSAGE&wsdlURL=wsdl%2Fmyservice.wsdl" />
<to uri="http4://localhost:8888/mockservice"/>
<log message="##### After soap provider out.body ##### ${out.body}" loggingLevel="INFO" />`
apache-camel
edited Nov 24 '18 at 8:42
Francesco Montesano
5,5232651
asked Nov 21 '18 at 19:46
stewchickenstewchicken
7611
add a comment |
I already got reply from to uri which is external soap service provider. but why I could not see the response in log with ${out.body} i think soap is InOut exchangepattern, it should have out.body always. My code example looks like below.
Any hints are more than welcome!
<from uri="cxf://http://localhost:8080/myservice?dataFormat=MESSAGE&wsdlURL=wsdl%2Fmyservice.wsdl" />
<to uri="http4://localhost:8888/mockservice"/>
<log message="##### After soap provider out.body ##### ${out.body}" loggingLevel="INFO" />`
apache-camel
edited Nov 24 '18 at 8:42
Francesco Montesano
5,5232651
asked Nov 21 '18 at 19:46
stewchickenstewchicken
7611
I already got reply from to uri which is external soap service provider. but why I could not see the response in log with ${out.body} i think soap is InOut exchangepattern, it should have out.body always. My code example looks like below.
Any hints are more than welcome!
<from uri="cxf://http://localhost:8080/myservice?dataFormat=MESSAGE&wsdlURL=wsdl%2Fmyservice.wsdl" />
<to uri="http4://localhost:8888/mockservice"/>
<log message="##### After soap provider out.body ##### ${out.body}" loggingLevel="INFO" />`
apache-camel
apache-camel
edited Nov 24 '18 at 8:42
Francesco Montesano
5,5232651
asked Nov 21 '18 at 19:46
stewchickenstewchicken
7611
edited Nov 24 '18 at 8:42
Francesco Montesano
5,5232651
asked Nov 21 '18 at 19:46
stewchickenstewchicken
7611
edited Nov 24 '18 at 8:42
Francesco Montesano
5,5232651
edited Nov 24 '18 at 8:42
Francesco Montesano
5,5232651
edited Nov 24 '18 at 8:42
Francesco Montesano
5,5232651
5,5232651
asked Nov 21 '18 at 19:46
stewchickenstewchicken
7611
asked Nov 21 '18 at 19:46
stewchickenstewchicken
7611
asked Nov 21 '18 at 19:46
stewchickenstewchicken
7611
7611
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The OUT message of a previous processor becomes the IN message of your log processor.
I would recommend to simply not use the OUT message. As long as you only work with the IN message, Camel takes care of the out message (copies the IN message).
Quote from the book Camel in Action:
In many cases, processors don’t set an out message, so in this case
the in message is reused.
answered Nov 23 '18 at 6:53
burkiburki
1,7431415
add a comment |
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%2f53419500%2fcould-not-display-out-body-at-log-for-external-soap-provider%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The OUT message of a previous processor becomes the IN message of your log processor.
I would recommend to simply not use the OUT message. As long as you only work with the IN message, Camel takes care of the out message (copies the IN message).
Quote from the book Camel in Action:
In many cases, processors don’t set an out message, so in this case
the in message is reused.
answered Nov 23 '18 at 6:53
burkiburki
1,7431415
add a comment |
The OUT message of a previous processor becomes the IN message of your log processor.
I would recommend to simply not use the OUT message. As long as you only work with the IN message, Camel takes care of the out message (copies the IN message).
Quote from the book Camel in Action:
In many cases, processors don’t set an out message, so in this case
the in message is reused.
answered Nov 23 '18 at 6:53
burkiburki
1,7431415
add a comment |
The OUT message of a previous processor becomes the IN message of your log processor.
I would recommend to simply not use the OUT message. As long as you only work with the IN message, Camel takes care of the out message (copies the IN message).
Quote from the book Camel in Action:
In many cases, processors don’t set an out message, so in this case
the in message is reused.
answered Nov 23 '18 at 6:53
burkiburki
1,7431415
The OUT message of a previous processor becomes the IN message of your log processor.
I would recommend to simply not use the OUT message. As long as you only work with the IN message, Camel takes care of the out message (copies the IN message).
Quote from the book Camel in Action:
In many cases, processors don’t set an out message, so in this case
the in message is reused.
answered Nov 23 '18 at 6:53
burkiburki
1,7431415
answered Nov 23 '18 at 6:53
burkiburki
1,7431415
answered Nov 23 '18 at 6:53
burkiburki
1,7431415
answered Nov 23 '18 at 6:53
burkiburki
1,7431415
1,7431415
add a comment |
add a comment |
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f53419500%2fcould-not-display-out-body-at-log-for-external-soap-provider%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
