Marshall Schor (JIRA | 23 Sep 22:01 2014
Picon

[jira] [Created] (UIMA-4020) extract JSON support from core sdk into addon, to avoid dependence on Jackson Jar

Marshall Schor created UIMA-4020:
------------------------------------

             Summary: extract JSON support from core sdk into addon, to avoid dependence on Jackson Jar
                 Key: UIMA-4020
                 URL: https://issues.apache.org/jira/browse/UIMA-4020
             Project: UIMA
          Issue Type: Task
          Components: Core Java Framework
    Affects Versions: 2.6.0SDK
            Reporter: Marshall Schor
            Assignee: Marshall Schor
            Priority: Minor
             Fix For: 2.6.1SDK

The current embedded JSON support makes the core UIMA SDK have a dependency in the Jackson core jar.  Move the
JSON support to a separate project, and restructure things so there's no dependency in the core on JSON things.

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Lou DeGenaro (JIRA | 23 Sep 20:53 2014
Picon

[jira] [Closed] (UIMA-4011) DUCC Common - DuccPropertiesResolver should not issue info message for loading private properties


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

Lou DeGenaro closed UIMA-4011.
------------------------------
    Resolution: Fixed

code is delivered.

> DUCC Common - DuccPropertiesResolver should not issue info message for loading private properties
> -------------------------------------------------------------------------------------------------
>
>                 Key: UIMA-4011
>                 URL: https://issues.apache.org/jira/browse/UIMA-4011
>             Project: UIMA
>          Issue Type: Bug
>          Components: DUCC
>            Reporter: Lou DeGenaro
>            Assignee: Lou DeGenaro
>            Priority: Minor
>             Fix For: 1.1.0-Ducc
>
>
> DuccPropertiesResolver is shared by CLI and WS.  It should not issue info messages when they should in fact
be debug messages.
> In particular, the loading of the ducc.private.properties file is best classified as a debugging type
message.  And an error message is issued if something goes wrong.

--
(Continue reading)

Lou DeGenaro (JIRA | 23 Sep 20:52 2014
Picon

[jira] [Reopened] (UIMA-4011) DUCC Common - DuccPropertiesResolver should not issue info message for loading private properties


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

Lou DeGenaro reopened UIMA-4011:
--------------------------------

Missed one spot.

> DUCC Common - DuccPropertiesResolver should not issue info message for loading private properties
> -------------------------------------------------------------------------------------------------
>
>                 Key: UIMA-4011
>                 URL: https://issues.apache.org/jira/browse/UIMA-4011
>             Project: UIMA
>          Issue Type: Bug
>          Components: DUCC
>            Reporter: Lou DeGenaro
>            Assignee: Lou DeGenaro
>            Priority: Minor
>             Fix For: 1.1.0-Ducc
>
>
> DuccPropertiesResolver is shared by CLI and WS.  It should not issue info messages when they should in fact
be debug messages.
> In particular, the loading of the ducc.private.properties file is best classified as a debugging type
message.  And an error message is issued if something goes wrong.

--
This message was sent by Atlassian JIRA
(Continue reading)

xia yongmin (JIRA | 23 Sep 09:39 2014
Picon

[jira] [Created] (UIMA-4019) It takes a long time for the sendCAS(cas) method to send a cas to the cas processor, when the cas processor is fast, then the sendCAS method is bottleneck.

xia yongmin created UIMA-4019:
---------------------------------

             Summary: It takes a long time for the sendCAS(cas) method to send a cas to the cas processor, when the cas
processor is fast, then the sendCAS method is bottleneck.
                 Key: UIMA-4019
                 URL: https://issues.apache.org/jira/browse/UIMA-4019
             Project: UIMA
          Issue Type: Question
          Components: Async Scaleout
            Reporter: xia yongmin

I have a CollectionReader, a Cas Processor and a Cas Consumer, it takes 1ms for CollectionReader to
initialize a cas, 5ms for Cas Processor to analyze, and 1ms for Cas Consumer to consume the cas.

it seems that I can deploy 5 instances of cas processor to obtain 5 times speed.

but when i did this, it didn't work like that.

And I found that it took a long time for the sendCAS(cas) method to send a cas from CollectionReader to Cas Processor.

how can I solve this problem?

many thanks.

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

(Continue reading)

Lou DeGenaro (JIRA | 22 Sep 17:06 2014
Picon

[jira] [Created] (UIMA-4018) DUCC Web Server (WS) javascript

Lou DeGenaro created UIMA-4018:
----------------------------------

             Summary: DUCC Web Server (WS) javascript 
                 Key: UIMA-4018
                 URL: https://issues.apache.org/jira/browse/UIMA-4018
             Project: UIMA
          Issue Type: Improvement
          Components: DUCC
            Reporter: Lou DeGenaro
            Assignee: Lou DeGenaro
            Priority: Minor
             Fix For: 1.1.0-Ducc

Move recusive call in timed-loop to end.

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Marshall Schor (JIRA | 20 Sep 05:18 2014
Picon

[jira] [Resolved] (UIMA-4017) plug maybe theoretical hole in setting up type systems


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

Marshall Schor resolved UIMA-4017.
----------------------------------
    Resolution: Fixed

> plug maybe theoretical hole in setting up type systems
> ------------------------------------------------------
>
>                 Key: UIMA-4017
>                 URL: https://issues.apache.org/jira/browse/UIMA-4017
>             Project: UIMA
>          Issue Type: Bug
>          Components: Core Java Framework
>    Affects Versions: 2.6.0SDK
>            Reporter: Marshall Schor
>            Assignee: Marshall Schor
>            Priority: Minor
>             Fix For: 2.6.1SDK
>
>
> in some settings, we've seen strange occasional errors that might be caused by concurrent
initialization of the built-in types.   Improve the bit of code that prevents this by making it work across
multiple threads.. 

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
(Continue reading)

Marshall Schor (JIRA | 20 Sep 05:15 2014
Picon

[jira] [Created] (UIMA-4017) plug maybe theoretical hole in setting up type systems

Marshall Schor created UIMA-4017:
------------------------------------

             Summary: plug maybe theoretical hole in setting up type systems
                 Key: UIMA-4017
                 URL: https://issues.apache.org/jira/browse/UIMA-4017
             Project: UIMA
          Issue Type: Bug
          Components: Core Java Framework
    Affects Versions: 2.6.0SDK
            Reporter: Marshall Schor
            Assignee: Marshall Schor
            Priority: Minor
             Fix For: 2.6.1SDK

in some settings, we've seen strange occasional errors that might be caused by concurrent initialization
of the built-in types.   Improve the bit of code that prevents this by making it work across multiple
threads.. 

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Richard Eckart de Castilho | 18 Sep 17:52 2014
Picon

JSON support introduces a new dependency in uimaj-core

Hi,

I have noticed that the new JSON support also introduces a new dependency on jackson in uimaj-core.
I wonder if that is a good idea since our users might need to get extra permission from their legal
departments to use the new library when they want to upgrade. Would it be reasonable to maintain
the JSON support in a separate module? Given the kind of very deep integration that the JSON
support appears to have, this might not even be easily possible.

What do you think?

Cheers,

-- Richard
Marshall Schor (JIRA | 18 Sep 17:32 2014
Picon

[jira] [Resolved] (UIMA-4015) logic hole in obscure case in MetaDataObject_impl


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

Marshall Schor resolved UIMA-4015.
----------------------------------
    Resolution: Fixed

> logic hole in obscure case in MetaDataObject_impl
> -------------------------------------------------
>
>                 Key: UIMA-4015
>                 URL: https://issues.apache.org/jira/browse/UIMA-4015
>             Project: UIMA
>          Issue Type: Bug
>          Components: Core Java Framework
>    Affects Versions: 2.6.0SDK
>            Reporter: Marshall Schor
>            Assignee: Marshall Schor
>            Priority: Minor
>             Fix For: 2.6.1SDK
>
>
> While reviewing the changes in MetaDataObject_impl, I noticed a path in writePrimitiveValue, which
wraps the primitive value with an "element-kind", like <element-kind>value</element-kind>.  For JSON
serialization, this is { "element-kind" : value }.  But for JSON this wrapping is not done if the value is a
string.  There's a logic bug in this case (which may not occur in practice?) - the skipping of the writing of
the closing } is not done, needs fixing.

--
(Continue reading)

Marshall Schor (JIRA | 18 Sep 17:18 2014
Picon

[jira] [Created] (UIMA-4016) add tests for toJSON methods of JSONizable

Marshall Schor created UIMA-4016:
------------------------------------

             Summary: add tests for toJSON methods of JSONizable
                 Key: UIMA-4016
                 URL: https://issues.apache.org/jira/browse/UIMA-4016
             Project: UIMA
          Issue Type: Test
          Components: Core Java Framework
    Affects Versions: 2.6.0SDK
            Reporter: Marshall Schor
            Priority: Minor
             Fix For: 2.6.1SDK

Add test cases for JSON serialization of Descriptors, especially Type System Descriptions, i.e. the
toJSON methods of JSONizable

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Marshall Schor (JIRA | 18 Sep 17:14 2014
Picon

[jira] [Created] (UIMA-4015) logic hole in obscure case in MetaDataObject_impl

Marshall Schor created UIMA-4015:
------------------------------------

             Summary: logic hole in obscure case in MetaDataObject_impl
                 Key: UIMA-4015
                 URL: https://issues.apache.org/jira/browse/UIMA-4015
             Project: UIMA
          Issue Type: Bug
          Components: Core Java Framework
    Affects Versions: 2.6.0SDK
            Reporter: Marshall Schor
            Assignee: Marshall Schor
            Priority: Minor
             Fix For: 2.6.1SDK

While reviewing the changes in MetaDataObject_impl, I noticed a path in writePrimitiveValue, which
wraps the primitive value with an "element-kind", like <element-kind>value</element-kind>.  For JSON
serialization, this is { "element-kind" : value }.  But for JSON this wrapping is not done if the value is a
string.  There's a logic bug in this case (which may not occur in practice?) - the skipping of the writing of
the closing } is not done, needs fixing.

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


Gmane