We have a route:

from("file:inbox?&probeContentType=true&preMove=inprogress/${file:name}&renameUsingCopy=true")
        .transacted()
        .bean(MimeTypeParser.class, "populateFileTypeHeaderFields")
        .to("seda:somewhere")
        
The probeContentType executes before preMove & renameUsingCopy and correctly
sets the Exchange.FILE_CONTENT_TYPE header.

The problem happens during the preMove & renameUsingCopy part where
GenericFileExpressionRenamer calls the GenericFile method GenericFile<T>
copyFrom(GenericFile<T> source).

This "copy constructor" method does not copy the header
Exchange.FILE_CONTENT_TYPE, nor does it preserve the value of the
GenericFile probeContentType field.

The class GenericFileRenameProcessStrategy calls
GenericFileExpressionRenamer from the method begin() which in turn calls
GenericFile.bindToExchange(Exchange exchange).

GenericFile.bindToExchange() clears all "CamelFile*" headers and then calls
GenericFile.populateHeaders(GenericFileMessage<T> message) which would call
Files.probeContentType(Path path) if the GenericFile probeContentType field
weren't now false.

When our route gets to the MimeTypeParser bean the "CamelFileContentType"
header is lost, and that is what we are looking for.

One work-around is to put something like this between .transacted() and the
.bean():

.process(exchange ->  {
     Path path = exchange.getIn().getBody(File.class).toPath();
     exchange.getIn().setHeader(Exchange.FILE_CONTENT_TYPE,
Files.probeContentType(path));
})



--
View this message in context: 
http://camel.465427.n5.nabble.com/Bug-using-File-endpoint-probeContentType-and-preMove-attributes-together-causes-Exchange-FILE-CONTEN-tp5805088.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Reply via email to