How to make URL char encoding between ftp gateway and notifier consistent

Solution Verified - Updated -

Issue

FTP notifier and FTP provider are not configured the same way what it comes to user name (and password).
I have one ftp user configured in a properties file and tried to use the following configurations:

<ftp-provider hostname="${ftp.host}">
   <ftp-bus>
    <ftp-message-filter password="${ftp.password}" protocol="ftp" username="${ftp.username}" 
   </ftp-bus>
</ftp-provider>
and
<NotificationList type="ok">
  <target class="NotifyFTP">
    <ftp
     URL="ftp://${ftp.username}:${ftp.password}@${ftp.host}" />
  </target>
</NotificationList>

In my case I have a "/" character in the username, and the ftp notifier fails. If I url-encode the username, then the notifier works, but ftp provider fails. Am I forced to have two usernames in the properties file? One url-encoded and one as plain text.

Environment

  • JBoss Enterprise SOA Platform(SOA-P) 5.2.0

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
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.