camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pontus Ullgren <ullg...@gmail.com>
Subject Re: Camel JCIFS issues detected
Date Mon, 20 Feb 2017 20:41:14 GMT
Thanks for reportin this.

However the camel-jcifs is part of camel-extra project[1] which has it's
own mailing list[2] and jira[3].


[1]: https://camel-extra.github.io/
[2]: http://camel-extra.1091541.n5.nabble.com/
[3]: https://camel-extra.atlassian.net/projects/CAMEX/summary

On Mon, 20 Feb 2017 at 17:42 Rene Suter <rene.suter-beck@bluewin.ch> wrote:

> Hi all
>
> I use currently Camel version 2.18.2 and Camel JCIFS version 2.15.0 for
> accessing Samba shares.
>
> The current implementation failes due a missing implementation in class
> org.apacheextras.camel.component.jcifs.SmbConsumer:
>
>     @Override
>     protected void updateFileHeaders(final GenericFile<SmbFile> file, final
> Message message) {
>         final long length = file.getFileLength();
>         final long modified = file.getLastModified();
>         file.setFileLength(length);
>         file.setLastModified(modified);
>         if (length >= 0)
>             message.setHeader(Exchange.FILE_LENGTH, length);
>         if (modified >= 0)
>             message.setHeader(Exchange.FILE_LAST_MODIFIED, modified);
>     }
>
>
> Additionally the rename function does not work when the file already exists
> in the target folder. Could you implement property 'renameUsingCopy' in the
> same way as it is available on file2.
>
> Is there a new version planned which solves this issue?
>
> regards
> René
>
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Camel-JCIFS-issues-detected-tp5794146.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message