Eclipse not display warning if try catch is not present

Thread view:

Mirror - 05 Apr 2007 16:14 GMT

Hello,
can you help me ?

i write this:
sf =    (SessionFactory) super
    .servlet
    .getServletContext()
    .getAttribute(
    HibernatePlugIn.SESSION_FACTORY_KEY);
hsession = sf.openSession();

the method signature is:
public org.hibernate.classic.Session openSession() throws
HibernateException;

Why eclipse not say that a try-catch block is missing ?

Thank's
Giulio

Reply to this Message

visionset - 05 Apr 2007 16:25 GMT

> the method signature is:
> public org.hibernate.classic.Session openSession() throws
> HibernateException;
>
> Why eclipse not say that a try-catch block is missing ?

Because it is a RuntimeException

--
Mike W

Reply to this Message

usenetuser@hotmail.co.uk - 05 Apr 2007 16:27 GMT

> Hello,
> can you help me ?
[quoted text clipped - 15 lines]
> Thank's
> Giulio

HibernateException inherits from RuntimeException... that's why. You
can still catch it if you want to, but you don't have to.

Reply to this Message

Jason Cavett - 05 Apr 2007 16:40 GMT

On Apr 5, 11:27 am, usenetu...@hotmail.co.uk wrote:

> > Hello,
> > can you help me ?
[quoted text clipped - 20 lines]
>
> - Show quoted text -

...and...from what I've learned about RuntimeExceptions, you shouldn't
really catch them anyway. If you're getting a RuntimeException you
have a deeper problem that needs fixed.

Reply to this Message

Uwe Plonus - 05 Apr 2007 16:48 GMT

> ...and...from what I've learned about RuntimeExceptions, you shouldn't
> really catch them anyway. If you're getting a RuntimeException you
> have a deeper problem that needs fixed.

Which is not true for HibernateException. In former versions of
hibernate it was not a RuntimeException. I don't know exactly why they
changed that but in the case of a HibernateException there are many ways
to continue.

Also other RuntimeExceptions are worth catching. Often you have the
possibility to continue.

Another thing are Errors. They are not worth of catching because you
can't do anything useful in case of an Error.

Uwe

Reply to this Message

Oliver Wong - 05 Apr 2007 17:37 GMT

>> ...and...from what I've learned about RuntimeExceptions, you shouldn't
>> really catch them anyway. If you're getting a RuntimeException you
[quoted text clipped - 10 lines]
> Another thing are Errors. They are not worth of catching because you
> can't do anything useful in case of an Error.

Unless, of course, the people at Hibernate decide to change
HibernateException so that it no longer subclasses (Runtime)Exception, but
Error instead. In which case, you should catch that error, as there *is*
something useful you can do with it.

In other words, forget the dogma. Catch an throwable if it makes sense
to do so, and don't catch it if it doesn't make sense to do so.

- Oliver

Reply to this Message

Jason Cavett - 05 Apr 2007 17:50 GMT

> >> ...and...from what I've learned about RuntimeExceptions, you shouldn't
> >> really catch them anyway. If you're getting a RuntimeException you
[quoted text clipped - 22 lines]
>
> - Show quoted text -

Good advice. Thanks.

Reply to this Message

Eclipse not display warning if try catch is not present

Free Magazines