[ 
https://issues.apache.org/jira/browse/CONNECTORS-1432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16052305#comment-16052305
 ] 

Kishore Kumar commented on CONNECTORS-1432:
-------------------------------------------

Hi [~daddywri],

The issue is with the javascript in how we handle the 
+checkSpecificationForSave+ and other check methods. What happens is, since we 
are using ajax and the base javascript is loaded once and most of the 
checkMethods are global, so if a previous page had a 
+s1_checkSpecificationForSave+ method, the current page will check if 
+checkSpecificationForSave+ method exists, if exists (since we have a method in 
global object from the previous page that gets executed).

In the above scenario, before adding the Tika Transformation connector, the 
File Output connector already added +s1_checkSpecificationForSave+ to the 
global window object, and after adding Tika, s1 is assigned to Tika and the old 
+s1_checkSpecificationForSave+ methods get executed (that method was actually 
added by File Output connector) and Tika Specs doesn't have any 
+checkSpecificationForSave+ method.

Fix:
I was previously removing only _checkConfig_ and +checkConfigForSave+ from the 
global window object whenever the user navigates to a different page, now I am 
also removing +checkSpecificationForSave+ and +checkSpecification+ from the 
global window object.

> Job with Tika will not save - no error popup
> --------------------------------------------
>
>                 Key: CONNECTORS-1432
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-1432
>             Project: ManifoldCF
>          Issue Type: Bug
>          Components: Tika extractor
>    Affects Versions: ManifoldCF 2.7
>         Environment: Ubuntu 16.10
> ElasticSearch
> File System
> Tika transform
>            Reporter: Steph van Schalkwyk
>            Assignee: Kishore Kumar
>             Fix For: ManifoldCF 2.8
>
>
> When adding Tika to a job, it will only (and then only some times) add if 
> this is the first configured job.
> All subsequent jobs added with Tika fail to save.
> Dropping the database solves it, but only for the first Job.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to