+1
[EMAIL PROTECTED] wrote:
> Hi All,
>
> In our project we have a problem with exception handling witch has been
> implemented like
>
> try {
>
> } catch (Exception e ) {
> //
> // code handle exception
> //
> }
>
> the easiest and fastest way.
>
> It would be nice if a refactoring could give us a splitup of all possible
> exceptions in the try .. catch block
>
> try {
>
> } catch ( IOException ne) {
> //
> // code handle exception
> //
> } catch ( SqlException ne) {
> //
> // code handle exception
> //
> } catch ( Exception ne) {
> //
> // code handle exception
> //
> }
>
> Where
> //
> // code handle exception
> //
> is copied in each entry of the refactored exception
>
>
> Jan
>
>
>
>
>
>
> Visit us at http://www.clearstream.com
>
> IMPORTANT MESSAGE
>
> Internet communications are not secure and therefore Clearstream International does
>not accept legal responsibility for the contents of this message.
>
> The information contained in this e-mail is confidential and may be legally
>privileged. It is intended solely for the addressee. If you are not the intended
>recipient, any disclosure, copying, distribution or any action taken or omitted to be
>taken in reliance on it, is prohibited and may be unlawful. Any views expressed in
>this e-mail are those of the individual sender, except where the sender specifically
>states them to be the views of Clearstream International or of any of its affiliates
>or subsidiaries.
>
> END OF DISCLAIMER
>
> _______________________________________________
> Eap-features mailing list
> [EMAIL PROTECTED]
> http://www.intellij.com/mailman/listinfo/eap-features
>
>
_______________________________________________
Eap-features mailing list
[EMAIL PROTECTED]
http://www.intellij.com/mailman/listinfo/eap-features
