Attachment: Added: helloworld.tar
Attachment: Added: server.log

Link: Added: This issue is related to SOA-1490

Link: Added: This issue is related to SOA-1491

Note from Kevin - this differs from SOA-1490 in that in 1490, the bug was how the ESB constructed the URL - in this problem (SOA-1873) the user must define the URL and encode all necessary chars - need to document an example - and verify that it works.

The correct way to use these chars in an FTP notifier password or dir is:

For example - for a dir of "ftp_dir##"

                                   <target class="NotifyFTP">
                                        <ftp
                                            URL="ftp://username:password@servername.jboss.com/ftp_dir%23%23"
                                           filename="test.{jbossesb.message.id}.dat"
                                           passive="true" />
                                   </target>

Link: Added: This issue depends JBESB-3147

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. I'll log a separate feature request JIRA for that.

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>

Link: Added: This issue is a dependency of SOA-1887

I have added this issue to the Release Notes.  Here is the draft text:


https://jira.jboss.org/jira/browse/SOA-1873
    

    There is an inconsistency between the FTP Gateway Listener and the FTP Notifier.
    The FTP Gateway Listener can accept non-alpha numeric characters for fields such as the
     password whilst the FTP Notifier cannot. For instance, a # character must be entered as %23
     to work in the Notifier. If you enter an illegal character, the Notifier will not work.

Also should be noted in the NotifyFTP section of the OOB chapters of the Programmers Guide

I have reworded the Release Note slightly:

https://jira.jboss.org/jira/browse/SOA-1873

    There is an inconsistency between the FTP Gateway Listener and the FTP Notifier. The
    FTP Gateway Listener can accept non-alpha numeric characters whilst the FTP Notifier
    cannot. In the latter case, fields must be URL encoded. For instance, a # character must be
    entered as %23 to work in the Notifier. If you enter an illegal character, the Notifier will not
    work.


As per Darrin's recommendation, the issue is also mentioned in the appropriate section of the Programmers' Guide now.