thanks everyone for your help. I resolved this issue. It turned out that it was in 2 parts. this is with Camel 2.15.1
1) my customer was first sending encrypted files with no compression. And the Camel Release 2.15.1 requires compression. 1.1) it still didn't work. 2) It was discovered that there was a bug in the customers code. Their code, they created the iostream but never actually wrote to it, only the unencrypted stream. so, it still boiled down to compression. thanks for your help, I hope this helps others. always verify the files using the command line, GnuPG. you can also apply trace on the Karaf container if you are using Jboss Fuse Karaf, or any other container to see if the data is compressed or not, and any problems that arise from it. So, I'm pleased and happy to report, it is not a Camel issue. ----- Gary Lee Mills -- View this message in context: http://camel.465427.n5.nabble.com/decrypting-with-PGPDataFormat-tp5793436p5793676.html Sent from the Camel - Users mailing list archive at Nabble.com.
