[
https://issues.apache.org/jira/browse/CONNECTORS-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16594885#comment-16594885
]
Karl Wright commented on CONNECTORS-1526:
-----------------------------------------
Noted that the getFile() method basically relies on DFC to tell us whether it
could get the file or not:
{code}
/** Write the content of the object to a file path.
*@param path is where the content should be written.
*@return the file path where the content was written. */
public String getFile(String path)
throws DocumentumException, RemoteException
{
try
{
return ((IDfSysObject)object).getFile(path);
}
catch (DfAuthenticationException ex)
{
throw new DocumentumException("Bad credentials:
"+ex.getMessage(),DocumentumException.TYPE_BADCREDENTIALS);
}
catch (DfIdentityException ex)
{
throw new DocumentumException("Bad docbase name:
"+ex.getMessage(),DocumentumException.TYPE_BADCONNECTIONPARAMS);
}
catch (DfDocbaseUnreachableException e)
{
throw new DocumentumException("Docbase unreachable:
"+e.getMessage(),DocumentumException.TYPE_SERVICEINTERRUPTION);
}
catch (DfIOException e)
{
throw new DocumentumException("Docbase io exception:
"+e.getMessage(),DocumentumException.TYPE_SERVICEINTERRUPTION);
}
catch (DfException dfe)
{
// Can't decide what to do without looking at the exception text.
// This is crappy but it's the best we can manage, apparently.
String errorMessage = dfe.getMessage();
if (errorMessage.indexOf("[DM_CONTENT_E_CANT_START_PULL]") != -1)
{
// It's probably not a transient error. Report it as an access
violation, even though it
// may well not be. We don't have much info as to what's happening.
throw new
DocumentumException(dfe.getMessage(),DocumentumException.TYPE_NOTALLOWED);
}
else if (errorMessage.indexOf("[DM_OBJECT_E_LOAD_INVALID_STRING_LEN]") !=
-1 ||
errorMessage.indexOf("[DM_PLATFORM_E_INTEGER_CONVERSION_ERROR]") != -1
||
errorMessage.indexOf("[DM_STORAGE_E_BAD_TICKET]") != -1)
{
throw new
DocumentumException(dfe.getMessage(),DocumentumException.TYPE_CORRUPTEDDOCUMENT);
}
// Treat it as transient, and retry
throw new
DocumentumException(dfe.getMessage(),DocumentumException.TYPE_SERVICEINTERRUPTION);
}
}
{code}
The only way to change the behavior is to essentially ignore the specific error
condition that's giving you problems, so I need to know which one that is.
> Empty contents are skipped completely/ignored in documentum connector
> ----------------------------------------------------------------------
>
> Key: CONNECTORS-1526
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1526
> Project: ManifoldCF
> Issue Type: Bug
> Components: Documentum connector
> Affects Versions: ManifoldCF 2.9.1
> Reporter: Divya Thejaswini
> Assignee: Karl Wright
> Priority: Major
>
> While fetching data from Documentum respository, empty documents are skipped
> completely instead of indexing its meta data.
> We need someone's help on fixing this in any of the upcoming version or patch
> for MCF 2.9.1 version.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
