SSDM-4005: New DSS FS (FTP / CIFS) resolvers: remove obsolete ftp information...

SSDM-4005: New DSS FS (FTP / CIFS) resolvers: remove obsolete ftp information from service.properties

SVN: 36936

openbis_oai_pmh/etc/service.properties

@@ -455,60 +455,5 @@ post-registration.post-registration-tasks = pathinfo-feeding
 post-registration.pathinfo-feeding.class = ch.systemsx.cisd.etlserver.path.PathInfoDatabaseFeedingTask
 # post-registration.pathinfo-feeding.compute-checksum = true
 
-#
-# FTP server configuration
-#
-# when set to 'true' an internal ftp server will be started. it provides users with an alternative 
-# way to interact with their data (i.e. via an FTP client).  
-#ftp.server.enable=false
-#
-# port where the FTP server will be started. Optional parameter, default value is 2121
-#ftp.server.port=2121
-#
-# Specifies a range of ports to be used when working in passive mode. The default value is "2130-2140",
-# meaning only 11 ports will be provide to connecting clients. If there are more than 11 concurrent 
-# users the configuration will have to be adjusted accordingly.  
-#ftp.server.passivemode.port.range=2130-2140
-#
-# Similar to the global 'use-ssl' parameter. When set to 'true' all 'keystore' properties become mandatory.
-#ftp.server.use-ssl=true
-#
-# maximum number of threads used by the internal FTP server. Defaults to 25.
-#ftp.server.maxThreads=25
-#
-# The virtual folder structure supplied by the FTP server looks like 
-#      ${space}/${project}/${experiment}/<data-set-level>
-# While the first 3 levels in the hierarchy are not configurable, the format of the '<data-set-level>' 
-# can be specified with a template using the following built-in variables : 
-# ${dataSetCode} - the data set code
-# ${dataSetType} - the data set type
-# ${dataSetDate} - the creation date of the data set
-# ${disambiguation} - if ${dataSetCode} is not used, the ${disambiguation} variable must be present 
-#                     in the template in order to avoid path collisions. 
-# ${fileName} - When ${fileName} is specified in the template, '<data-set-level>' will include 
-#     the name of a file located directly under the dataset root folder. One entry will be created 
-#     for earch such file. 
-# Example :
-# ftp.server.dataset.display.template=${dataSetDate}-${disambiguation}-${fileName}
-# Result :
-# /SPACE/PROJECT/EXPERIMENT/2011-10-10-10-10-A-file1.txt
-# /SPACE/PROJECT/EXPERIMENT/2011-10-10-10-10-A-file2.pdf
-# /SPACE/PROJECT/EXPERIMENT/2011-10-10-10-10-B-file1.txt
-# /SPACE/PROJECT/EXPERIMENT/2011-10-10-10-10-B-file2.pdf
-#
-# Optional parameter, default template value is ${dataSetCode}                
-#ftp.server.dataset.display.template=${dataSetCode}
-#
-# Specifies that the contents of a dataset should be listed starting from a preconfigured subpath. 
-# The property is only configurable per data set type.
-# Example (will hide a single top level folder starting with 'orig' for datasets of type HCS_IMAGE):
-#   ftp.server.dataset.filelist.subpath.HCS_IMAGE = orig[^/]*
-#ftp.server.dataset.filelist.subpath.<dataset-type>=
-#
-# A filter pattern appiled to all files within a data set. Files not matching the pattern will be 
-# hidden and FTP users will not see them.
-# Example (will only show PNG files for data sets of type HCS_IMAGE): 
-# ftp.server.dataset.filelist.filter.HCS_IMAGE= .*png
-
 jython-version=2.7