$collection-uri | The collection-uri where resources should be stored. Collection URIs can be specified either as a simple collection path or an XMLDB URI. |
$directory | The directory in the file system from where the files are read. |
$pattern | The file matching pattern. Based on code from Apache's Ant, thus following the same conventions. For example: *.xml matches any file ending with .xml in the current directory, **/*.xml matches files in any directory below the current one |
$collection-uri | The collection-uri where resources should be stored. Collection URIs can be specified either as a simple collection path or an XMLDB URI. |
$directory | The directory in the file system from where the files are read. |
$pattern | The file matching pattern. Based on code from Apache's Ant, thus following the same conventions. For example: *.xml matches any file ending with .xml in the current directory, **/*.xml matches files in any directory below the current one |
$mime-type | If the mime-type is something other than 'text/xml' or 'application/xml', the resource will be stored as a binary resource. |
$collection-uri | The collection-uri where resources should be stored. Collection URIs can be specified either as a simple collection path or an XMLDB URI. |
$directory | The directory in the file system from where the files are read. |
$pattern | The file matching pattern. Based on code from Apache's Ant, thus following the same conventions. For example: *.xml matches any file ending with .xml in the current directory, **/*.xml matches files in any directory below the current one |
$mime-type | If the mime-type is something other than 'text/xml' or 'application/xml', the resource will be stored as a binary resource. |
$preserve-structure | If preserve-structure is true(), the filesystem directory structure will be mirrored in the collection. Otherwise all the matching resources, including the ones in sub-directories, will be stored in the collection given in the first argument flatly. |