db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthew T. Adams (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JDO-478) [Fatal Error] messages are printed to stdout/stderr during negative test case runs of JDOHelperConfigTest
Date Fri, 08 Jun 2007 05:18:26 GMT

    [ https://issues.apache.org/jira/browse/JDO-478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502661
] 

Matthew T. Adams commented on JDO-478:
--------------------------------------

Although this appears to be fixed, the fix is to register an anonymous ErrorHandler class
in JDOHelper that throws the SAXExceptions given on error and fatalError, and simply swallows
the one given on warning.

We need to consider whether to allow the JDO implementation to register its own ErrorHandler.


> [Fatal Error] messages are printed to stdout/stderr during negative test case runs of
JDOHelperConfigTest
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: JDO-478
>                 URL: https://issues.apache.org/jira/browse/JDO-478
>             Project: JDO
>          Issue Type: Bug
>          Components: api2
>         Environment: JDK 1.4
>            Reporter: Matthew T. Adams
>            Assignee: Matthew T. Adams
>            Priority: Minor
>             Fix For: JDO 2 maintenance release 1
>
>         Attachments: JDO-478.patch
>
>
> During execution of JDOHelperConfigTest negative test cases, the message "[Fatal Error]
:-1:-1: Premature end of file." is printed to stdout or stderr, even though the errors are
expected and don't indicate unexpected exceptions.
> Probably need to register an error handler with the XML parser to capture these messages.

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


Mime
View raw message