You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Paulex Yang (JIRA)" <ji...@apache.org> on 2006/08/31 05:17:29 UTC
[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
[ 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