uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marshall Schor (JIRA)" <...@uima.apache.org>
Subject [jira] [Resolved] (UIMA-3675) Allow Eclilpse debugger to inspect more UIMA internals
Date Tue, 18 Mar 2014 20:37:46 GMT

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

Marshall Schor resolved UIMA-3675.
----------------------------------

    Resolution: Fixed

> Allow Eclilpse debugger to inspect more UIMA internals
> ------------------------------------------------------
>
>                 Key: UIMA-3675
>                 URL: https://issues.apache.org/jira/browse/UIMA-3675
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Core Java Framework
>    Affects Versions: 2.5.0SDK
>            Reporter: Marshall Schor
>            Assignee: Marshall Schor
>            Priority: Minor
>             Fix For: 2.5.1SDK
>
>
> While debugging something, I got frustrated by the value inspector of Eclipse saying
something like ... exception.. instead of the value.  The internet suggested that hashCode
throwing exceptions might be the cause.  I found several of the internal UIMA objects had
hashCode set to throw unsupportedException - and changed those to some reasonable hash code,
it allowed the Eclipse debugger to show the values of these objects.  Fixup some of these
and improve the toString methods, for better debugging capability.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message