Mailinglist Archive: yast-devel (81 mails)

< Previous Next >
Re: [yast-devel] About catching exceptions
  • From: Klaus Kaempf <kkaempf@xxxxxxx>
  • Date: Thu, 22 Apr 2010 14:17:33 +0200
  • Message-id: <20100422121733.GA22964@xxxxxxxxxxxxx>
* Martin Vidner <mvidner@xxxxxxx> [Apr 22. 2010 12:05]:
On Thu, Apr 22, 2010 at 11:36:58AM +0200, Klaus Kaempf wrote:
when calling functions known to raise exceptions, its always good
practice to enclose calls with begin ... rescue ... end and catch
exceptions locally.

Good that you bring it up because I think that you got it absolutely

Unless you give more specific examples, this only creates more
problems by bypassing the generic, well-thought out system-wide
recue from.

Yes, you're right. I stand corrected.

CORRECT, unknown exceptions are handled by exception_trap in

My problem is rest-service, not web-client.

Apparently the exception trap in rest-service is not sufficient.

See bnc#598794 where the rest-service errors out (presumably) because
of a permission error but this isn't shown in the rest-service logs.

And the web-client interpretes this as 503 Service Unavailable without
any hints about the real cause.

SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG N├╝rnberg)

To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: yast-devel+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups