You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Burn Lewis (JIRA)" <de...@uima.apache.org> on 2016/07/21 13:03:20 UTC

[jira] [Closed] (UIMA-5022) Some Dd2Spring errors are lost and confusing

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

Burn Lewis closed UIMA-5022.
----------------------------
    Resolution: Fixed

Putt all Saxon errors on the console so none hidden when it calls exit.  Fix the importbyname-failed one by returning a null instead of a message that is treated as a relative file.  Now have to stop on the first error in the deployment descriptor ... but later errors are often caused by the first,

> Some Dd2Spring errors are lost and confusing
> --------------------------------------------
>
>                 Key: UIMA-5022
>                 URL: https://issues.apache.org/jira/browse/UIMA-5022
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>            Reporter: Burn Lewis
>            Assignee: Burn Lewis
>            Priority: Minor
>             Fix For: 2.8.2SDK
>
>
> When dd2spring cannot resolve an import-by-name it returns an error message that is interpreted as a relative file name which produces a strange message such as:
>   FODC0005: java.io.FileNotFoundException:
>   /users10/ducc/apache_ducc_runtime/apache-uima/bin/ERROR converting import by name to
>   absolute path (No such file or directory)
> Also some Saxon errors (e.g. cannot access file) are lost when the Transform class exits before the calling code can log them.



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