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] Resolved: (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 05:29:23 GMT
     [ http://issues.apache.org/jira/browse/HARMONY-1345?page=all ]

Paulex Yang resolved HARMONY-1345.
----------------------------------

    Resolution: Fixed

Richard, patch applied at revision r438803, thanks a lot for this enhancement, please verify
that the problem is fully fixed as you expected.

BTW, I noticed this patch includes serialization test for SQLWarning, it's fine, but my concern
is this enhancement is irrevelant with and is not included in this JIRA/patch description,
and I'm not sure if they are included by your intention, so I think it would be better if
you separate them to another issue.

> [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