Thanks for the link !
I found an example in
https://github.com/apache/camel/blob/master/components/camel-jetty/src/test/java/org/apache/camel/component/jetty/HttpSendFileTest.java
I have noticed from the example
https://github.com/apache/camel/blob/master/components/camel-jetty/src/test/j
loos like it's the cxf behaviour to decode the base64. but I could not find
this in cxf docs.
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-cxf-component-is-encoding-base64-by-default-tp5750705p5752303.html
Sent from the Camel - Users mailing list archive at Nabble.co
Normally CXF interceptors can take care of the message marshalling (encoding
base 64) and unmarshalling (decoding base 64) out of box.
But in camel-cxf we have some data formats which can help user deal with the
low level message.
You can find more information about these data formats here[1]
[1
camel-http component support to send RequestEntity by default.
If you want to send a file as a multi part form, you can just put the
MultipartRequestEntity instance into the message body, just like this.
private RequestEntity createMultipartRequestEntity() throws Exception {
File file = n
HI
Are you saying that file in remote machine should be added as network drive
1st and the i need to use file component to pick up. Is my understanding is
correct.
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-configuration-to-pick-up-file-from-Shared-location-and-re
OK, i have solved the problem and it is not a Camel or ActiveMQ but a
Protocol Buffers issue.
I do not understand the problem yet but this does not work with ZXing:
But if i do this it decoding works
Only by creating a local reference to a copy of an internal byte array of
ByteString.
--
Vi
Hi I configured my route as bellow
filename=DataMoveCommand
config.fileloc = \\Server\\FileLoc
I mapped shared location \\Remote_Server\\FileLoc as network drive
when I bring my camel context up in logs found like as bellow
Route: route18 st
