[jira] [Commented] (CONNECTORS-875) LiveLink connector: LAPI exceptions not always caught

[ https://issues.apache.org/jira/browse/CONNECTORS-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13887973#comment-13887973 ] David Morana commented on CONNECTORS-875: - Thanks, Is it possible to get a pat

[jira] [Commented] (CONNECTORS-875) LiveLink connector: LAPI exceptions not always caught

[ https://issues.apache.org/jira/browse/CONNECTORS-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13887856#comment-13887856 ] Karl Wright commented on CONNECTORS-875: r1563151 fixes the rest. > LiveLink

[jira] [Resolved] (CONNECTORS-875) LiveLink connector: LAPI exceptions not always caught

[ https://issues.apache.org/jira/browse/CONNECTORS-875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-875. Resolution: Fixed > LiveLink connector: LAPI exceptions not always caught > ---

[jira] [Commented] (CONNECTORS-875) LiveLink connector: LAPI exceptions not always caught

[ https://issues.apache.org/jira/browse/CONNECTORS-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13887832#comment-13887832 ] Karl Wright commented on CONNECTORS-875: r1563147 refactors how threads handle

[jira] [Created] (CONNECTORS-876) Livelink connector: when HTTP error code 500 is returned, the error message should contain some identifying information

Karl Wright created CONNECTORS-876: -- Summary: Livelink connector: when HTTP error code 500 is returned, the error message should contain some identifying information Key: CONNECTORS-876 URL: https://issues.apache

Re: [VOTE] Release Apache ManifoldCF 1.5, RC6

I should add that, in order to assure myself that CONNECTORS-872 was indeed "fixed", I tried the following using the client's exact web connection and job parameters: - single-process example, Windows, java 7 - multiprocess-file-example, Windows, java 7 - single-process example, Ubuntu, java 6 - m

[jira] [Created] (CONNECTORS-875) LiveLink connector: LAPI exceptions not always caught

Karl Wright created CONNECTORS-875: -- Summary: LiveLink connector: LAPI exceptions not always caught Key: CONNECTORS-875 URL: https://issues.apache.org/jira/browse/CONNECTORS-875 Project: ManifoldCF

Re: Difference between fetch and read activity

Hi Karl, I asked that because I'm trying to use same variable names as other authors used. Good to know that it depends on author. I thought that I'm missing something. Thank you. 2014-01-31 Karl Wright : > Hi Muhammed, > > It is up to the connector's author to determine what activities are us

Re: Difference between fetch and read activity

Hi Muhammed, It is up to the connector's author to determine what activities are useful and what they should record. Since the connectors have multiple authors, then of course they have multiple activities meaning roughly the same thing. You really need to look in the context of a single connect

Difference between fetch and read activity

Example Docs4U connector has protected final static String ACTIVITY_FETCH = "fetch"; Filesystem connector has protected final static String ACTIVITY_READ = "read document"; Alfresco and GoogleDrive connector have both of them and use ACTIVITY_FETCH instead of ACTIVITY_READ for activity history.