Yes agree, I also get the same behaviour from a similare route when running Camel 2.17.1.
Could you create a issue in Jira for this. // Pontus On Wed, 8 Jun 2016 at 17:23 nicolasduminil < [email protected]> wrote: > Hello, > > Thanks for your reply. So, what you're saying is that > org.apache.camel.dataformat.tarfile.TarElementInputStreamWrapper would be > an > input stream, right ? In this case I don't need to convert it, just could > read from it. But I tried the following: > > from("direct:unzip").unmarshal().gzip() > .split(new TarSplitter()) > .to("file:{{file.unzip.path}}?fileName=${file:name}"); > > The file-system structure gets correctly created, I mean folders, > sub-folders, etc., until the file level. But all the files are created with > 0 blocks, i.e. empty. Do you have any idea of what might happening here ? > > Many thanks in advance, > > Nicolas > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Trying-to-use-the-TarSplitter-tp5783658p5783722.html > Sent from the Camel - Users mailing list archive at Nabble.com. >
