1．Do you need an exception type that isn't represented by those in the Java platform?
2．Would it help users if they could differentiate your exceptions from those thrown by classes written by other vendors?
3．Does your code throw more than one related exception?
4．If you use someone else's exceptions, will users have access to those exceptions? A similar question is, should your package be independent and self-contained?
15 个解决方案
#1
1、项目是分层分模块的 ,不可能你一个项目你一个人开发...
统一了异常就是统一了对外异常展示的方式
还有很多原因呢.....
统一了异常就是统一了对外异常展示的方式
还有很多原因呢.....
#2
有时一些模块不需要某些问题通过，想要直接结束掉，就用异常模式！
一个子模块的某个异常可以导致整个过程全部结束，进入最后的异常处理。
这样可以节省很多判断！
一个子模块的某个异常可以导致整个过程全部结束，进入最后的异常处理。
这样可以节省很多判断！
#3
该回复于2010-12-17 14:22:46被版主删除
#4
举个例子吧 假如说有个业务需求 返回1就应该报异常 但是JAVA 里面自带的不会有这种异常 ，这时候就需要自己定异常了！
#5
什么业务会有这样的场景？
#6
If you use someone else's exceptions, will users have access to those exceptions? A similar question is, should your package be independent and self-contained?
#7
java里是有很多的异常处理，不一定都是符合实际项目的，实际中要根据项目的需求在自定义异常的。
#8
一言难尽啊。
#9
比如，公交卡充值系统可能不支持一次性冲入1000元之类的。
#10
自定义异常是为了设置异常链的起点。一般情况下，我们都是允许每个程序员看到所有的异常信息，这个时候大多数都是把下一层的异常直接重掷到上一层。然而在多层次的结构中，我们有时候需要隐藏底层异常（这种异常的信息很多，很枯燥） ，而给消费者提供一个更为直观的异常，这个时候我们需要自定义异常。有的异常类jdk已经给我们提供，比如常用的IllegalArgumentException。如果你想在此再作包装，你可以创建自己的异常类。如此，消费者将以此异常作为异常链的起点。
#11
1．Do you need an exception type that isn't represented by those in the Java platform?
answer: yes,do need. sometimes the personal business does require it just like the upper one said.
2．Would it help users if they could differentiate your exceptions from those thrown by classes written by other vendors?
answer: yes, it helps. i think if they could differentiate them, it could help them to better understand the situation when the exception occurs.
3．Does your code throw more than one related exception?
answer: yes, it does. including those exceptions from the java platform, some of them are related with each other.i think it maybe could inhance the systematic property of the exceptions.it just proves they are integrated into one platform.
4．If you use someone else's exceptions, will users have access to those exceptions? A similar question is, should your package be independent and self-contained?
answer: maybe they have not. my package should be independent and self-contained. why? maybe loose coupling makes it.
就像楼上说的具体业务的要求，系统异常不可能面面俱到，自定义就是为了在实际中填补应用空白，另外的，自己的一套关联度强的异常可控性高，识别度高，和平台异常搭配使用，满足业务需求和系统需求。
answer: yes,do need. sometimes the personal business does require it just like the upper one said.
2．Would it help users if they could differentiate your exceptions from those thrown by classes written by other vendors?
answer: yes, it helps. i think if they could differentiate them, it could help them to better understand the situation when the exception occurs.
3．Does your code throw more than one related exception?
answer: yes, it does. including those exceptions from the java platform, some of them are related with each other.i think it maybe could inhance the systematic property of the exceptions.it just proves they are integrated into one platform.
4．If you use someone else's exceptions, will users have access to those exceptions? A similar question is, should your package be independent and self-contained?
answer: maybe they have not. my package should be independent and self-contained. why? maybe loose coupling makes it.
就像楼上说的具体业务的要求，系统异常不可能面面俱到，自定义就是为了在实际中填补应用空白，另外的，自己的一套关联度强的异常可控性高，识别度高，和平台异常搭配使用，满足业务需求和系统需求。
#12
创建自定义异常是为了表示应用程序的一些错误类型，为代码可能发生的一个或多个问题提供新含义。可以显示代码多个位置之间的错误的相似性，也可区分代码运行时可能出现的相似问题的一个或多个错误，或给出应用程序中一组错误的特定含义。
http://book.csdn.net/bookfiles/150/1001506505.shtml
楼主看看这个吧。
http://book.csdn.net/bookfiles/150/1001506505.shtml
楼主看看这个吧。
#13
我感觉就是有些异常在程序中来说的话 没有问题 代码上是不会报错的
但是放到业务逻辑中，这种情况就是不允许的。
比如楼上说的充值问题，代码没有问题，也不会报错。
当然还有就是为了规范
但是放到业务逻辑中，这种情况就是不允许的。
比如楼上说的充值问题，代码没有问题，也不会报错。
当然还有就是为了规范
#14
系统中，有些异常会有不同的处理方式，你可能需要知道异常返回的值之类的，自定义的话就可以控制返回值了
#15
没有就问题来回答问题
#1
1、项目是分层分模块的 ,不可能你一个项目你一个人开发...
统一了异常就是统一了对外异常展示的方式
还有很多原因呢.....
统一了异常就是统一了对外异常展示的方式
还有很多原因呢.....
#2
有时一些模块不需要某些问题通过，想要直接结束掉，就用异常模式！
一个子模块的某个异常可以导致整个过程全部结束，进入最后的异常处理。
这样可以节省很多判断！
一个子模块的某个异常可以导致整个过程全部结束，进入最后的异常处理。
这样可以节省很多判断！
#3
该回复于2010-12-17 14:22:46被版主删除
#4
举个例子吧 假如说有个业务需求 返回1就应该报异常 但是JAVA 里面自带的不会有这种异常 ，这时候就需要自己定异常了！
#5
什么业务会有这样的场景？
#6
If you use someone else's exceptions, will users have access to those exceptions? A similar question is, should your package be independent and self-contained?
#7
java里是有很多的异常处理，不一定都是符合实际项目的，实际中要根据项目的需求在自定义异常的。
#8
一言难尽啊。
#9
比如，公交卡充值系统可能不支持一次性冲入1000元之类的。
#10
自定义异常是为了设置异常链的起点。一般情况下，我们都是允许每个程序员看到所有的异常信息，这个时候大多数都是把下一层的异常直接重掷到上一层。然而在多层次的结构中，我们有时候需要隐藏底层异常（这种异常的信息很多，很枯燥） ，而给消费者提供一个更为直观的异常，这个时候我们需要自定义异常。有的异常类jdk已经给我们提供，比如常用的IllegalArgumentException。如果你想在此再作包装，你可以创建自己的异常类。如此，消费者将以此异常作为异常链的起点。
#11
1．Do you need an exception type that isn't represented by those in the Java platform?
answer: yes,do need. sometimes the personal business does require it just like the upper one said.
2．Would it help users if they could differentiate your exceptions from those thrown by classes written by other vendors?
answer: yes, it helps. i think if they could differentiate them, it could help them to better understand the situation when the exception occurs.
3．Does your code throw more than one related exception?
answer: yes, it does. including those exceptions from the java platform, some of them are related with each other.i think it maybe could inhance the systematic property of the exceptions.it just proves they are integrated into one platform.
4．If you use someone else's exceptions, will users have access to those exceptions? A similar question is, should your package be independent and self-contained?
answer: maybe they have not. my package should be independent and self-contained. why? maybe loose coupling makes it.
就像楼上说的具体业务的要求，系统异常不可能面面俱到，自定义就是为了在实际中填补应用空白，另外的，自己的一套关联度强的异常可控性高，识别度高，和平台异常搭配使用，满足业务需求和系统需求。
answer: yes,do need. sometimes the personal business does require it just like the upper one said.
2．Would it help users if they could differentiate your exceptions from those thrown by classes written by other vendors?
answer: yes, it helps. i think if they could differentiate them, it could help them to better understand the situation when the exception occurs.
3．Does your code throw more than one related exception?
answer: yes, it does. including those exceptions from the java platform, some of them are related with each other.i think it maybe could inhance the systematic property of the exceptions.it just proves they are integrated into one platform.
4．If you use someone else's exceptions, will users have access to those exceptions? A similar question is, should your package be independent and self-contained?
answer: maybe they have not. my package should be independent and self-contained. why? maybe loose coupling makes it.
就像楼上说的具体业务的要求，系统异常不可能面面俱到，自定义就是为了在实际中填补应用空白，另外的，自己的一套关联度强的异常可控性高，识别度高，和平台异常搭配使用，满足业务需求和系统需求。
#12
创建自定义异常是为了表示应用程序的一些错误类型，为代码可能发生的一个或多个问题提供新含义。可以显示代码多个位置之间的错误的相似性，也可区分代码运行时可能出现的相似问题的一个或多个错误，或给出应用程序中一组错误的特定含义。
http://book.csdn.net/bookfiles/150/1001506505.shtml
楼主看看这个吧。
http://book.csdn.net/bookfiles/150/1001506505.shtml
楼主看看这个吧。
#13
我感觉就是有些异常在程序中来说的话 没有问题 代码上是不会报错的
但是放到业务逻辑中，这种情况就是不允许的。
比如楼上说的充值问题，代码没有问题，也不会报错。
当然还有就是为了规范
但是放到业务逻辑中，这种情况就是不允许的。
比如楼上说的充值问题，代码没有问题，也不会报错。
当然还有就是为了规范
#14
系统中，有些异常会有不同的处理方式，你可能需要知道异常返回的值之类的，自定义的话就可以控制返回值了
#15
没有就问题来回答问题