This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 94144 - From Forum: CachedRowSetDataProvider's commitChanges()'s exception
Summary: From Forum: CachedRowSetDataProvider's commitChanges()'s exception
Status: NEW
Alias: None
Product: obsolete
Classification: Unclassified
Component: visualweb (show other bugs)
Version: 5.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: John Baker
Depends on:
Reported: 2007-02-02 21:30 UTC by bugbridge
Modified: 2008-02-27 07:48 UTC (History)
1 user (show)

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description bugbridge 2007-02-02 21:30:13 UTC
Original submitter: sakthivelg

Description: (sakthivelg)
>> * CachedRowSetDataProvider's commitChanges()'s exception
>> *commitChanges() should create & throw DataProviderException instead of
RuntimeException, as it looks from method's signatore that, that was the intention.
>> And at the moment, DataProviderException looks very basic. I think it should
also contain all information which can be used/parsed to create meaningful
message i.e. same facility as one has in CachedRowSet.
>> Any thoughts?

Evaluation: (jbaker)
CachedRowSetDataProvider's commitChanges does throw a DataProviderException.
But, DataProviderException is a runtime exception.
From the post it appears that the Customer would like the DataProviderException
to show more info, but what info?

Please get more info from the Customer, thank you

Evaluation (Entry 2): (jbaker)
Just a quick comment, the subcategory database, is for Java DB, not
dataproviders :-)

Evaluation (Entry 3):
Comments from customer:
Hi John,
That???s correct.
But I was referring to actual SQL Exceptions which could be passed to
DataProviderException, so that if required, developer at his own liberty could
use/parse them in his own way to display to end user on screen.
Something like commitChanges() does, it parses and constitutes a message in its
own way, may be one would like to make message in different way.

When there is a SyncResolverException, We just throw a RuntimeException(message)
instead of wrapping the SQLException.
In cases, users wanting to catch SQLExcetpion for specific cases to display
custom message, they could do so, if SQLException is passed with