harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paulex Yang (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (HARMONY-1345) [classlib][sql] java.sql.SQLWarning#setNextWarning(SQLWarning ex) should add the SQLWarning ex to the end of the SQLWarning chain rather than replacing the next exception directly
Date Thu, 31 Aug 2006 03:17:29 GMT
     [ http://issues.apache.org/jira/browse/HARMONY-1345?page=all ]

Paulex Yang reassigned HARMONY-1345:
------------------------------------

    Assignee: Paulex Yang

> [classlib][sql] java.sql.SQLWarning#setNextWarning(SQLWarning ex) should add the SQLWarning
ex to the end of the SQLWarning chain rather than replacing the next exception directly
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HARMONY-1345
>                 URL: http://issues.apache.org/jira/browse/HARMONY-1345
>             Project: Harmony
>          Issue Type: Bug
>          Components: Classlib
>            Reporter: Richard Liang
>         Assigned To: Paulex Yang
>         Attachments: Harmony-1345.zip
>
>
> Hello,
> java.sql.SQLWarning#setNextWarning(SQLWarning ex) should add the SQLWarning ex to the
end of the SQLWarning chain rather than replacing the next exception directly. And method
getNextWarning acts differently from RI when the chain has an object which is an instance
of SQLException(which is added by the setNextException method)but not a SQLWaring.
> I will attach a patch to fix this issue.
> Best regards,
> Richard

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message