Issue 2938: how to report database-or-infrastructure-level erros as exceptions (pids-rtf2)
Source: Level Seven Visualizations (Mr. Jon Farmer, jon(at)level7vis.com)
Nature: Uncategorized Issue
Severity: 
Summary: Is there an exception, or a "correct way"  to let the client know that an
underlying infrastructure error (like an RDBMS error) has occurred?

Resolution: 
Revised Text: 
Actions taken:
September 20, 1999: received issue
Discussion: 

End of Annotations:=====
Reply-To: "Jon Farmer" <jfarmer@ic.net>
From: "Jon Farmer" <jfarmer@ic.net>
To: "pids-rtf2" <pids-rtf2@emerald.omg.org>
Subject: how to report database-or-infrastructure-level erros as
exceptions
Date: Mon, 20 Sep 1999 11:58:42 -0400
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.2106.4
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4
Content-Type: text/plain;
	charset="iso-8859-1"
X-UIDL: 599d3facc609c6877dec5a83fc707ed4

Is there an exception, or a "correct way"  to let the client know that
an
underlying infrastructure error (like an RDBMS error) has occurred?

Jon

Date: Mon, 20 Sep 1999 09:45:48 -0700
From: Tim Brinson <TBrinson@mindspring.com>
Reply-To: TBrinson@2ab.com
Organization: 2ab
X-Mailer: Mozilla 4.5 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Jon Farmer <jfarmer@ic.net>
CC: pids-rtf2 <pids-rtf2@emerald.omg.org>
Subject: Re: how to report database-or-infrastructure-level erros as
exceptions
References: <003401bf0381$0b9df8f0$34c8869d@JGFNT.toledolink.com>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii
X-UIDL: a38b9d53a9462475a732001b54e9c45e

Jon Farmer wrote:

> Is there an exception, or a "correct way"  to let the client know
that an
> underlying infrastructure error (like an RDBMS error) has occurred?

You can raise a system exception (as opposed to a user exception) for
this.
Any operation can raise system exceptions  - they are not declared in
the
raises clause.  These are defined as in the CORBA specification.  I
don't
think there are well defined semantics for each system exception but
you can
get an idea from their names which to use.

You could post a question to the ORBOS list for any suggestions which
to use
for an RDBMS error.  You might want to look them up in the CORBA spec
first
to be sure you are asking an educated question (the ORBOS list is not
for
nubbies).

Tim

X-Sender: bburt@mindspring.com
X-Mailer: Windows Eudora Pro Version 3.0 (32)
Date: Mon, 20 Sep 1999 12:05:48 -0500
To: "Jon Farmer" <jfarmer@ic.net>, "pids-rtf2"
<pids-rtf2@emerald.omg.org>
From: Bob Burt <bburt@2ab.com>
Subject: Re: how to report database-or-infrastructure-level erros as
  exceptions
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-UIDL: 3ec6449c94df75792f261dc39b150125

Perhaps PERSIST_STORE, reference in CORBA 2.3 at 3.17.1.16 for RDBMS
errors.

At 11:58 AM 9/20/99 -0400, Jon Farmer wrote:
>Is there an exception, or a "correct way"  to let the client know
that an
>underlying infrastructure error (like an RDBMS error) has occurred?
>
>Jon
>
>