The "vfs" transport is a polling based transport - i.e. it gets kicked off at
specified periodic durations, and would iterate through a list of directories or files
specified according to poll durations. When scanning a directory, it will match
its contents against a given regex to find the set of input files. For compressed
files, the contents could be matched against a regex to find individual files.
Each of these files thus found would be submitted as an Axis2 "message" into the
Axis2 engine.
The processed files would be deleted or renamed as specified in the configuration
Supported VFS example URIs
file:///directory/filename.ext
file:////somehost/someshare/afile.txt
jar:../lib/classes.jar!/META-INF/manifest.mf
zip:http://somehost/downloads/somefile.zip
jar:zip:outer.zip!/nested.jar!/somedir
jar:zip:outer.zip!/nested.jar!/some%21dir
tar:gz:http://anyhost/dir/mytar.tar.gz!/mytar.tar!/path/in/tar/README.txt
tgz:file://anyhost/dir/mytar.tgz!/somepath/somefile
gz:/my/gz/file.gz
http://somehost:8080/downloads/somefile.jar
http://myusername@somehost/index.html
webdav://somehost:8080/dist
ftp://myusername:mypassword@somehost/pub/downloads/somefile.tgz[?passive=true]
sftp://myusername:mypassword@somehost/pub/downloads/somefile.tgz
smb://somehost/home
axis2.xml - transport definition
enable|disable ?
services.xml - service attachment
required parameters
..
..
optional parameters
..
..
..
..
..
..
..
FTP testing URIs
ftp://ftpuser:password@asankha/somefile.csv?passive=true
ftp://vfs:apache@vfs.netfirms.com/somepath/somefile.xml?passive=true