topic Re: FOLDER NAME IS INVALID in Alfresco Archive

FOLDER NAME IS INVALID

joyola83 — Tue, 17 Jun 2014 19:39:03 GMT

I am trying to copy a directory to ALFRESCO using CIFS.cp -R /data/* /opt/ALFRESCO/Sitios/mi-sitio/documentLibraryI've mounted /opt/ALFRESCO before in /etc/fstab.But I got this exception:Constraint: 05170022 Value 'LISTA. CHOFERES. VEHICULOS.EXP.CENTAURO.' is not valid as a file name. This property

Re: FOLDER NAME IS INVALID

sanket — Mon, 08 Sep 2014 11:22:30 GMT

If this is your folder name 'LISTA. CHOFERES. VEHICULOS.EXP.CENTAURO.', then the problem is that its ending with a '.'.
Try removing the '.' at the end of its name; and you will be able to create it.
You can create your custom rule in the arriving alfresco folder which will normalize (strip) the invalid chars.

Re: FOLDER NAME IS INVALID

joyola83 — Mon, 08 Dec 2014 22:02:53 GMT

Thanks for your response. Also I've found that it's possible to disable the error.

<strong>IntegrityChecker.java</strong>
<java>
        if (failOnViolation && !warnOnly)
        {
            logger.error(sb.toString());
            throw new IntegrityException(sb.toString(), failures);
        }
        else
        {
            logger.warn(sb.toString());
            // no exception
        }
</java>

But I dont know hot to set failOnViolation in false.

Any idea?

Re: FOLDER NAME IS INVALID

joyola83 — Mon, 08 Dec 2014 22:21:38 GMT

I've found that it's possible to update this properties.

<blockcode>
#
# Enable system model integrity checking.
# WARNING: Changing this is unsupported; bugs may corrupt data
system.integrity.enabled=true
# Do integrity violations fail transactions
# WARNING: Changing this is unsupported; bugs may corrupt data
system.integrity.failOnViolation=true
# The number of errors to report when violations are detected
system.integrity.maxErrorsPerTransaction=5
# Add call stacks to integrity events so that errors are logged with possible causes
# WARNING: This is expensive and should only be switched on for diagnostic purposes
system.integrity.trace=false
</blockcode>

But there are same warning that it's not a good idea to change this value.

I'm importing a existing file system using the bulk import tool, and I have a lot of file that dont respect the default pattern to be a valid name. And it's not possible to change the file manually.

Any idea?

Re: FOLDER NAME IS INVALID

mrogers — Tue, 09 Dec 2014 09:42:09 GMT

You probably don't want to disable the integrity checker. Since that checks many different constraints. Perhaps remove the specific name constraint? Or change the pattern ?

However the name constraint is there for a reason and if you change it then you will be incompatible with things that expect windows like filesystems. (The repo itself couldn't care less and will be fine with any name. Although there will be a limit on the filename length.)