You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ctakes.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2013/06/14 20:44:21 UTC

[jira] [Commented] (CTAKES-210) Allow loading of Resources from InputStream instead of physical File

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

ASF subversion and git services commented on CTAKES-210:
--------------------------------------------------------

Commit 1493198 from chenpei@apache.org
[ https://svn.apache.org/r1493198 ]

CTAKES-209, CTAKES-210 -  With the new SentenceDetector working with OpenNLP 1.5, we can simplify how models are loaded now.
- Deleted the SuffixMaxentModelResourceImpl and related classes. It's just a string to the model file now.
- Deleted duplicated SentenceDectector.xml descriptors that were scattered.
- Added util in FileLocator.java to read in resources from InputStream instead of physical path File.  Updated the SD to use this mechanism.
                
> Allow loading of Resources from InputStream instead of physical File
> --------------------------------------------------------------------
>
>                 Key: CTAKES-210
>                 URL: https://issues.apache.org/jira/browse/CTAKES-210
>             Project: cTAKES
>          Issue Type: Improvement
>          Components: ctakes-core
>    Affects Versions: 3.0-incubating
>            Reporter: Pei Chen
>            Priority: Minor
>             Fix For: 3.1
>
>
> File or Url.getRawPath() became problematic if they are read in from the jars from the classpath and which couldn't resolve to a physical File.
> a.       Suggestion: Wherever possible, replace loading of resouces via java.io.File with InputStream instead.  . We can add a new method in the FileLocator util and deprecate the old File method.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira