Return-Path: X-Original-To: apmail-ctakes-notifications-archive@www.apache.org Delivered-To: apmail-ctakes-notifications-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D97C817B2D for ; Sat, 11 Oct 2014 15:57:33 +0000 (UTC) Received: (qmail 48701 invoked by uid 500); 11 Oct 2014 15:57:33 -0000 Delivered-To: apmail-ctakes-notifications-archive@ctakes.apache.org Received: (qmail 48658 invoked by uid 500); 11 Oct 2014 15:57:33 -0000 Mailing-List: contact notifications-help@ctakes.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ctakes.apache.org Delivered-To: mailing list notifications@ctakes.apache.org Received: (qmail 48648 invoked by uid 99); 11 Oct 2014 15:57:33 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 11 Oct 2014 15:57:33 +0000 Date: Sat, 11 Oct 2014 15:57:33 +0000 (UTC) From: "jay vyas (JIRA)" To: notifications@ctakes.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CTAKES-320) Methods used by getDefaultPipeline should be able to load reasonable defaults without expecting external files. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CTAKES-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jay vyas updated CTAKES-320: ---------------------------- Description: In CTAKES-314, its evident that some simple pipelines break because of files which are expected to be on the classpath. Also, in one of the builders, I noticed it wanted this file {{org/apache/ctakes/dictionary/lookup/LookupDesc_Db.xml}} to be in place. Lets - create *some unit tests which ensure that *some reasonable defaults* can be loaded - This can be done using using {{Class.getResource...}} and embedding some term dictionaries in jars or - maybe by making a *direct URL connection on the fly to a stable server somewhere*, so it can download some reasonable defaults for external data files into {{/tmp/}} or something with a log warning that it wasnt able to find local resources.). Generally relying on unpacked jars not going to work in a distributed environment. was: In CTAKES-314, its evident that some simple pipelines break because of files which are expected to be on the classpath. Also, in one of the builders, I noticed it wanted this file {{org/apache/ctakes/dictionary/lookup/LookupDesc_Db.xml}} to be in place. Lets - create *some unit tests which ensure that *some reasonable defaults* can be loaded - This can be done using using Class.getResource or - maybe by making a direct URL connection on the fly to a stable server somewhere, so it can download some reasonable defaults for external data files into {{/tmp/}} or something with a log warning that it wasnt able to find local resources.). > Methods used by getDefaultPipeline should be able to load reasonable defaults without expecting external files. > ----------------------------------------------------------------------------------------------------------------- > > Key: CTAKES-320 > URL: https://issues.apache.org/jira/browse/CTAKES-320 > Project: cTAKES > Issue Type: Bug > Components: ctakes-clinical-pipeline > Affects Versions: 3.2.0 > Reporter: jay vyas > Fix For: 3.2.1 > > > In CTAKES-314, its evident that some simple pipelines break because of files which are expected to be on the classpath. > Also, in one of the builders, I noticed it wanted this file {{org/apache/ctakes/dictionary/lookup/LookupDesc_Db.xml}} to be in place. > Lets > - create *some unit tests which ensure that *some reasonable defaults* can be loaded > - This can be done using using {{Class.getResource...}} and embedding some term dictionaries in jars or > - maybe by making a *direct URL connection on the fly to a stable server somewhere*, so it can download some reasonable defaults for external data files into {{/tmp/}} or something with a log warning that it wasnt able to find local resources.). > Generally relying on unpacked jars not going to work in a distributed environment. -- This message was sent by Atlassian JIRA (v6.3.4#6332)