Feature request - consistent requirement for URL char encoding between ftp gateway and notifier ----------------------------------------------------------------------------------------------- Key: JBESB-3157 URL: https://jira.jboss.org/jira/browse/JBESB-3157 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.7 Reporter: Len DiMaggio Priority: Minor We're inconsistent with how we handle special characters between ftp gateway listener definitions and ftp notifier definitions - it would make it simpler for users if we handled these in the same way. For example, to use a directory of "ftp_dir##" and a password of "password##: FTP gateway listener: <ftp-provider hostname="servername.com" name="FTPprovider"> <ftp-bus busid="notifyFTPChannel"> <ftp-message-filter directory="/ftp_dir##" error-delete="false" error-suffix=".HAS_ERROR" input-suffix=".notifiertest" passive="true" password="password##" post-delete="false" post-suffix=".COMPLETE" username="username" work-suffix=".esbWorking" /> </ftp-bus> </ftp-provider> FTP: notifier: <action class="org.jboss.soa.esb.actions.Notifier" name="notify"> <property name="okMethod" value="notifyOK" /> <property name="notification-details"> <NotificationList type="OK"> <target class="NotifyFTP"> <ftp URL="ftp://username:password%23%23@servername.com/ftp_dir%23%23" filename="{jbossesb.message.id}.notifier" passive="true" /> </target> </NotificationList> </property> </action> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira