09-27-2016 02:06 AM
In our SMB/CIFS server implementation based on JLAN we want to make all files read-only. Thus, we set the read-only flag in the org.alfresco.jlan.server.filesys.FileInfo object. But it looks like that this is ignored.
Also the little example in the JLAN distribution jlanConfig.xml doesn't work. That is, a file with read-only permissions is presented by the SMB/CIFS server of the example as a writable file. I've looked into the source code of class org.alfresco.jlan.smb.server.disk.JavaFileDiskDriver. Line 104 and 115 in method buildFileInformation() reveal that the read-only flag of java.io.File object is transferred to the FileInfo object.
09-27-2016 04:54 AM
As I mentioned in my other response the JLAN project nowadays is primarily maintained as part of the Alfresco ECM product. The library itself does not see that much "action" as most of the integration logic is maintained in a different module / source path. As far as I can say from the usage within Alfresco, the read-only flag in FileInfo is properly handled as Alfresco itself exposes nodes in read-only state the same way depending on locks set on a particular node as well as effective permissions set on it.
09-27-2016 04:54 AM
As I mentioned in my other response the JLAN project nowadays is primarily maintained as part of the Alfresco ECM product. The library itself does not see that much "action" as most of the integration logic is maintained in a different module / source path. As far as I can say from the usage within Alfresco, the read-only flag in FileInfo is properly handled as Alfresco itself exposes nodes in read-only state the same way depending on locks set on a particular node as well as effective permissions set on it.
Tags
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.