You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@manifoldcf.apache.org by "Karl Wright (JIRA)" <ji...@apache.org> on 2011/08/12 14:13:27 UTC

[jira] [Resolved] (CONNECTORS-226) Usage and meaning of ManifoldCFException type REPOSITORY_CONNECTION_ERROR needs to be reviewed and clarified

     [ https://issues.apache.org/jira/browse/CONNECTORS-226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Karl Wright resolved CONNECTORS-226.
------------------------------------

       Resolution: Fixed
    Fix Version/s: ManifoldCF 0.3

r1157065


> Usage and meaning of ManifoldCFException type REPOSITORY_CONNECTION_ERROR needs to be reviewed and clarified
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: CONNECTORS-226
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-226
>             Project: ManifoldCF
>          Issue Type: Bug
>          Components: Framework core, JCIFS connector, LiveLink connector
>    Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3
>            Reporter: Karl Wright
>            Assignee: Karl Wright
>             Fix For: ManifoldCF 0.3
>
>
> The ManifoldCFException type REPOSITORY_CONNECTION_ERROR seems to be treated by the framework somewhat inconsistently.  In some places it is treated as a permanent connection exception, and in others as a temporary connection exception (in lieu of a ServiceInterruption where ServiceInterruption is not possible).  Only two connectors use it (LiveLink and jCIFS), and the JCIFS case is not interesting.  So really this is currently here to support Livelink.
> There are two ways forward.  The first way is to convert the Livelink connector's exception to a true ServiceInterruption, and revert REPOSITORY_CONNECTION_ERROR to its original meaning, which has now been deprecated as a result of the fact that connect() methods can no longer throw ManifoldCFExceptions at all.  The second is to continue the current Livelink-style usage, and make ALL usages consistent with that.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira