Handling large xml payloads in apache camel cxf
I am writing a camel proxy route to invoke an external web service. It so happens that the payload of the target service is pretty big. How do I handle this scenario in the route.
Coming from OSB background, in OSB, this is done by using chunked streaming mode. How can we achieve similar results in Apache camel.
The issue that I am facing with the normal payload data format route is that invocations are failing with Control Character issues as explained in my previous question : Apache Camel CXF - Error Illegal character ((CTRL-CHAR, code 31)
apache-camel cxf
asked Nov 28 '18 at 10:28
Sumit BauraiSumit Baurai
385
add a comment |
I am writing a camel proxy route to invoke an external web service. It so happens that the payload of the target service is pretty big. How do I handle this scenario in the route.
Coming from OSB background, in OSB, this is done by using chunked streaming mode. How can we achieve similar results in Apache camel.
The issue that I am facing with the normal payload data format route is that invocations are failing with Control Character issues as explained in my previous question : Apache Camel CXF - Error Illegal character ((CTRL-CHAR, code 31)
apache-camel cxf
asked Nov 28 '18 at 10:28
Sumit BauraiSumit Baurai
385
add a comment |
I am writing a camel proxy route to invoke an external web service. It so happens that the payload of the target service is pretty big. How do I handle this scenario in the route.
Coming from OSB background, in OSB, this is done by using chunked streaming mode. How can we achieve similar results in Apache camel.
The issue that I am facing with the normal payload data format route is that invocations are failing with Control Character issues as explained in my previous question : Apache Camel CXF - Error Illegal character ((CTRL-CHAR, code 31)
apache-camel cxf
asked Nov 28 '18 at 10:28
Sumit BauraiSumit Baurai
385
I am writing a camel proxy route to invoke an external web service. It so happens that the payload of the target service is pretty big. How do I handle this scenario in the route.
Coming from OSB background, in OSB, this is done by using chunked streaming mode. How can we achieve similar results in Apache camel.
The issue that I am facing with the normal payload data format route is that invocations are failing with Control Character issues as explained in my previous question : Apache Camel CXF - Error Illegal character ((CTRL-CHAR, code 31)
apache-camel cxf
apache-camel cxf
asked Nov 28 '18 at 10:28
Sumit BauraiSumit Baurai
385
asked Nov 28 '18 at 10:28
Sumit BauraiSumit Baurai
385
asked Nov 28 '18 at 10:28
Sumit BauraiSumit Baurai
385
asked Nov 28 '18 at 10:28
Sumit BauraiSumit Baurai
385
asked Nov 28 '18 at 10:28
Sumit BauraiSumit Baurai
385
385
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
You should consider Jetty,
Servlet or
Http4 (better control on the request) camel components. Theses http endpoints are designed to proxify http requests. With bridgeEndpoint and disableStreamCache options, you can create a http proxy with streaming without loading the payload in memory.
answered Dec 3 '18 at 17:06
ThomasThomas
56521129
At the moment, I am using the cxf component to proxy the webservices so that I dont have to construct the Soap response / fault structures. If I use the http4 camel component, would that still be taken care of or would I have to construct the response ...
– Sumit Baurai
Dec 5 '18 at 11:04
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%2f53517273%2fhandling-large-xml-payloads-in-apache-camel-cxf%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
You should consider Jetty,
Servlet or
Http4 (better control on the request) camel components. Theses http endpoints are designed to proxify http requests. With bridgeEndpoint and disableStreamCache options, you can create a http proxy with streaming without loading the payload in memory.
answered Dec 3 '18 at 17:06
ThomasThomas
56521129
At the moment, I am using the cxf component to proxy the webservices so that I dont have to construct the Soap response / fault structures. If I use the http4 camel component, would that still be taken care of or would I have to construct the response ...
– Sumit Baurai
Dec 5 '18 at 11:04
add a comment |
You should consider Jetty,
Servlet or
Http4 (better control on the request) camel components. Theses http endpoints are designed to proxify http requests. With bridgeEndpoint and disableStreamCache options, you can create a http proxy with streaming without loading the payload in memory.
answered Dec 3 '18 at 17:06
ThomasThomas
56521129
At the moment, I am using the cxf component to proxy the webservices so that I dont have to construct the Soap response / fault structures. If I use the http4 camel component, would that still be taken care of or would I have to construct the response ...
– Sumit Baurai
Dec 5 '18 at 11:04
add a comment |
You should consider Jetty,
Servlet or
Http4 (better control on the request) camel components. Theses http endpoints are designed to proxify http requests. With bridgeEndpoint and disableStreamCache options, you can create a http proxy with streaming without loading the payload in memory.
answered Dec 3 '18 at 17:06
ThomasThomas
56521129
You should consider Jetty,
Servlet or
Http4 (better control on the request) camel components. Theses http endpoints are designed to proxify http requests. With bridgeEndpoint and disableStreamCache options, you can create a http proxy with streaming without loading the payload in memory.
answered Dec 3 '18 at 17:06
ThomasThomas
56521129
answered Dec 3 '18 at 17:06
ThomasThomas
56521129
answered Dec 3 '18 at 17:06
ThomasThomas
56521129
answered Dec 3 '18 at 17:06
ThomasThomas
56521129
56521129
At the moment, I am using the cxf component to proxy the webservices so that I dont have to construct the Soap response / fault structures. If I use the http4 camel component, would that still be taken care of or would I have to construct the response ...
– Sumit Baurai
Dec 5 '18 at 11:04
add a comment |
At the moment, I am using the cxf component to proxy the webservices so that I dont have to construct the Soap response / fault structures. If I use the http4 camel component, would that still be taken care of or would I have to construct the response ...
– Sumit Baurai
Dec 5 '18 at 11:04
At the moment, I am using the cxf component to proxy the webservices so that I dont have to construct the Soap response / fault structures. If I use the http4 camel component, would that still be taken care of or would I have to construct the response ...
– Sumit Baurai
Dec 5 '18 at 11:04
At the moment, I am using the cxf component to proxy the webservices so that I dont have to construct the Soap response / fault structures. If I use the http4 camel component, would that still be taken care of or would I have to construct the response ...
– Sumit Baurai
Dec 5 '18 at 11:04
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.
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%2f53517273%2fhandling-large-xml-payloads-in-apache-camel-cxf%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
