Picon
Favicon

[jira] Created: (UIMA-663) CDE Resource Dependency page throwing NPE if XML missing <resourceManagerConfiguration> element

CDE Resource Dependency page throwing NPE if XML missing <resourceManagerConfiguration> element
-----------------------------------------------------------------------------------------------

                 Key: UIMA-663
                 URL: https://issues.apache.org/jira/browse/UIMA-663
             Project: UIMA
          Issue Type: Bug
          Components: Eclipse plugins
            Reporter: Marshall Schor
            Assignee: Marshall Schor
             Fix For: 2.2.1

CDE Resource Dependency page throwing NPE if XML missing <resourceManagerConfiguration> element. 
Visual effect is that the area of the screen for showing external resource bindings is not redrawn.

This only occurs if the <resourceManagerConfiguration> element is completely missing.  It works if it is
there but "empty":
<resourceManagerConfiguration/>.

Bug found during linux testing of CDE for 2.2.1, but also happens on Windows.

--

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Picon
Favicon

[jira] Closed: (UIMA-663) CDE Resource Dependency page throwing NPE if XML missing <resourceManagerConfiguration> element


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

Marshall Schor closed UIMA-663.
-------------------------------

    Resolution: Fixed

> CDE Resource Dependency page throwing NPE if XML missing <resourceManagerConfiguration> element
> -----------------------------------------------------------------------------------------------
>
>                 Key: UIMA-663
>                 URL: https://issues.apache.org/jira/browse/UIMA-663
>             Project: UIMA
>          Issue Type: Bug
>          Components: Eclipse plugins
>            Reporter: Marshall Schor
>            Assignee: Marshall Schor
>             Fix For: 2.2.1
>
>
> CDE Resource Dependency page throwing NPE if XML missing <resourceManagerConfiguration> element. 
Visual effect is that the area of the screen for showing external resource bindings is not redrawn.
> This only occurs if the <resourceManagerConfiguration> element is completely missing.  It works if it is
there but "empty":
> <resourceManagerConfiguration/>.
> Bug found during linux testing of CDE for 2.2.1, but also happens on Windows.

--

-- 
(Continue reading)

Picon
Favicon

[jira] Created: (UIMA-664) CustomResourceFactory_impl not catching exceptions when calling out to initialize method

CustomResourceFactory_impl not catching exceptions when calling out to initialize method
----------------------------------------------------------------------------------------

                 Key: UIMA-664
                 URL: https://issues.apache.org/jira/browse/UIMA-664
             Project: UIMA
          Issue Type: Improvement
          Components: Core Java Framework
            Reporter: Marshall Schor
            Assignee: Marshall Schor
            Priority: Minor
             Fix For: 2.2.1

While testing the CDE, found an instance where a custom resource was incorrectly configured (things were
missing that it needed in the class path).  The result of this was a silent failure to start the CDE editor,
although an entry was noted in the Eclipse error log.  This was because the missing class path caused a
NoClassDefFound exception to be thrown, but nobody (except the top-most Eclipse UI code) caught it.

I think the right place for putting a try/catch is around the point in the CustomResourceFactory where it
calls out to that resource's "initialize" method.  If that throws an exception, it should be caught and
wrapped with a new ResourceInitializationException, which says that the nested exception happened
while trying to initialize the custom resource, and identifying the custom resource.

--

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Michael Baessler | 3 Dec 11:39
Picon

Re: uimaj-2.2.1-03 ready for testing

The message:

'tar: A lone zero block at *'

is just a warning and can be ignored. All content is extracted 
correctly. The reason for the message is that newer tar versions expects 
two empty records
marking the end of the archive but it seems that our Maven build only 
creates one.
I tested with the latest Maven version 2.0.8 but it seems that the error 
still occurs.

I also found the following Maven issue:
http://jira.codehaus.org/browse/MNG-2762

-- Michael

Michael Baessler wrote:
> Michael Baessler wrote:
>> I have uploaded the latest release candidate for release 2.2.1 to
>> people.a.o:/home/mbaessler/distributions/uimaj-2.2.1/03
>>
>> So we can start testing with this level.
>>
>> --Michael
>>
> I seems that we have some issues with the tar.gz archives...
>
> With an older version of GNU tar (1.13) all works fine. With a newer 
> version (1.15) we got errors while decompressing the archive.
(Continue reading)

Picon
Favicon

[jira] Created: (UIMA-665) sometimes the test testHasNextWithOutOfMemoryError() for test class CpmCollectionReader_ErrorTest fails

sometimes the test testHasNextWithOutOfMemoryError() for test class CpmCollectionReader_ErrorTest fails
-------------------------------------------------------------------------------------------------------

                 Key: UIMA-665
                 URL: https://issues.apache.org/jira/browse/UIMA-665
             Project: UIMA
          Issue Type: Bug
          Components: Collection Processing
    Affects Versions: 2.2.1
            Reporter: Michael Baessler
            Assignee: Michael Baessler
             Fix For: 2.2.1

sometimes this test case fails... I will investigate the issue

--

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Picon
Favicon

[jira] Commented: (UIMA-665) sometimes the test testHasNextWithOutOfMemoryError() for test class CpmCollectionReader_ErrorTest fails


    [
https://issues.apache.org/jira/browse/UIMA-665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12547870
] 

Michael Baessler commented on UIMA-665:
---------------------------------------

It seems that the error is caused by the test case itself. The test assumes that the last call to the
StatusCallbackListener is the call that caused the error and the CAS for this call is null. But this is not
correct. It can happen that the second last call to the StatusCallbackListener has the error and so on the
last call the CAS is not null. The StatusCallbackListener already checks if an error is reported that the
CAS is null, so I will just remove the wrong assumption in the test case that the last CAS going through the
StatusCallbackListener must be null. 

> sometimes the test testHasNextWithOutOfMemoryError() for test class
CpmCollectionReader_ErrorTest fails
> -------------------------------------------------------------------------------------------------------
>
>                 Key: UIMA-665
>                 URL: https://issues.apache.org/jira/browse/UIMA-665
>             Project: UIMA
>          Issue Type: Bug
>          Components: Collection Processing
>    Affects Versions: 2.2.1
>            Reporter: Michael Baessler
>            Assignee: Michael Baessler
>             Fix For: 2.2.1
>
>
(Continue reading)

Picon
Favicon

[jira] Closed: (UIMA-665) sometimes the test testHasNextWithOutOfMemoryError() for test class CpmCollectionReader_ErrorTest fails


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

Michael Baessler closed UIMA-665.
---------------------------------

    Resolution: Fixed

> sometimes the test testHasNextWithOutOfMemoryError() for test class
CpmCollectionReader_ErrorTest fails
> -------------------------------------------------------------------------------------------------------
>
>                 Key: UIMA-665
>                 URL: https://issues.apache.org/jira/browse/UIMA-665
>             Project: UIMA
>          Issue Type: Bug
>          Components: Collection Processing
>    Affects Versions: 2.2.1
>            Reporter: Michael Baessler
>            Assignee: Michael Baessler
>             Fix For: 2.2.1
>
>
> sometimes this test case fails... I will investigate the issue

--

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
(Continue reading)

Picon
Favicon

[jira] Closed: (UIMA-664) CustomResourceFactory_impl not catching exceptions when calling out to initialize method


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

Marshall Schor closed UIMA-664.
-------------------------------

    Resolution: Fixed

> CustomResourceFactory_impl not catching exceptions when calling out to initialize method
> ----------------------------------------------------------------------------------------
>
>                 Key: UIMA-664
>                 URL: https://issues.apache.org/jira/browse/UIMA-664
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Core Java Framework
>            Reporter: Marshall Schor
>            Assignee: Marshall Schor
>            Priority: Minor
>             Fix For: 2.2.1
>
>
> While testing the CDE, found an instance where a custom resource was incorrectly configured (things were
missing that it needed in the class path).  The result of this was a silent failure to start the CDE editor,
although an entry was noted in the Eclipse error log.  This was because the missing class path caused a
NoClassDefFound exception to be thrown, but nobody (except the top-most Eclipse UI code) caught it.
> I think the right place for putting a try/catch is around the point in the CustomResourceFactory where it
calls out to that resource's "initialize" method.  If that throws an exception, it should be caught and
wrapped with a new ResourceInitializationException, which says that the nested exception happened
(Continue reading)

Picon
Favicon

[jira] Reopened: (UIMA-639) udpate ReleaseNotes for release 2.2.1


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

Michael Baessler reopened UIMA-639:
-----------------------------------

> udpate ReleaseNotes for release 2.2.1
> -------------------------------------
>
>                 Key: UIMA-639
>                 URL: https://issues.apache.org/jira/browse/UIMA-639
>             Project: UIMA
>          Issue Type: Bug
>          Components: Build, Packaging and Test
>    Affects Versions: 2.2.1
>            Reporter: Michael Baessler
>            Assignee: Michael Baessler
>             Fix For: 2.2.1
>
>

--

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Picon
Favicon

[jira] Closed: (UIMA-639) udpate ReleaseNotes for release 2.2.1


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

Michael Baessler closed UIMA-639.
---------------------------------

    Resolution: Fixed

> udpate ReleaseNotes for release 2.2.1
> -------------------------------------
>
>                 Key: UIMA-639
>                 URL: https://issues.apache.org/jira/browse/UIMA-639
>             Project: UIMA
>          Issue Type: Bug
>          Components: Build, Packaging and Test
>    Affects Versions: 2.2.1
>            Reporter: Michael Baessler
>            Assignee: Michael Baessler
>             Fix For: 2.2.1
>
>

--

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

(Continue reading)


Gmane