Camel file's tempPrefix does not work correctly if the target is Windows UNC path

Solution Verified - Updated -

Issue

  • If windows UNC path is used in the file producer, it does not take the actual path which starts with double backward slash "\ \" when creating the temp file. Instead, it only takes one "\" and creates a file relative to the local directory (C:)
  • Windows network UNC paths not treated correctly (File2/tempPrefix)

Environment

  • Red Hat Fuse
    • 7.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In