BeanException type is no longer necessary.

[GoogleCodeExporter]

Please describe a summary of the new feature (in a paragraph):

BeanException class, which is used to report BeanUtil related exceptions,
can be replaced with XerialException type by merging BeanErrorCode into
XerialErrorCode. 

The rationale for this change is that BeanException class does not convey
additional information except the BeanException specific error code. And
thus, developers can write an error-specific handler code in a catch
clause, as follows:

try
{
  // some method that might through an exception
}
catch(XerialException e)
{
   switch(e.getXerialErrorCode())
   {
      case InvalidBeanClass:
         ....
      case InvalidXMLData:
         ...
   }
}

Please provide any additional information below:

Original issue reported on code.google.com by taroleo on 10 Sep 2009 at 6:17

[GoogleCodeExporter]

done in [3574]

Original comment by taroleo on 10 Sep 2009 at 6:55

• Changed state: Fixed