RE: [Springframework-developer] DataBinder < BindException

[Rim, M. <mar...@cs...>]

i'm not asking for it to be changed. a major change like that will probably =
have to wait until after 1.0 is released. i'm trying to get a deeper =
understanding of the framework.

just from the names, it seems to me that BindException should extend =
Exception. but where i have trouble is, the justification for DataBinder =
extending BindException. does a DataBinder also need to be thrown and be =
treated as an Errors instance =3F or is it convenient to re-use some of the =
BindException routines in DataBinder =3F

a lot of the routines in BindException look like they'd be useful in a =
something that would bind values to beans ...



> -----Original Message-----
> From: j=FCrgen h=F6ller [werk3AT] [mailto:jue...@we...]
> Sent: Thursday, November 13, 2003 5:36 PM
> To: spr...@li...
> Subject: Re: [Springframework-developer] DataBinder < BindException
>=20
>=20
> That's an early design decision that goes to back to Rod's=20
> original com.interface21 version of the framework. As far as=20
> I understand the rationale, BindException extends Exception=20
> because this allows to throw the binding status as exception=20
> if binding errors are to be considered fatal. The thrown=20
> exception can then be treated as Errors instance for=20
> convenient checking of the contained errors. This is of=20
> course a rarely used feature, as binding errors are normally=20
> not considered fatal.
> =20
> Unfortunately, this has the disadvantage of having not only=20
> BindException but also its subclasses in the "Exceptions"=20
> category of the generated javadoc. I'm not really happy about=20
> that, but the alternative of dropping the exception feature=20
> and thus not making BindException an Exception also involves=20
> the obvious need to rename that default implementation of the=20
> Errors interface. That in turn would mean changing the=20
> signatures of quite a few template methods in the command and=20
> form controllers, breaking current implementations.
> =20
> I'm not sure if such a change is worth the effort... What do=20
> others think=3F
> =20
> Juergen

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D
This message is for the named person's use only. It may contain sensitive and=
 =
private proprietary or legally privileged information. No confidentiality or =
privilege is waived or lost by any mistransmission. If you are not the =
intended recipient, please immediately delete it and all copies of it from =
your system, destroy any hard copies of it and notify the sender. You must =
not, directly or indirectly, use, disclose, distribute, print, or copy any =
part of this message if you are not the intended recipient. CREDIT SUISSE =
GROUP and each legal entity in the CREDIT SUISSE FIRST BOSTON or CREDIT SUISS=
E=
 ASSET MANAGEMENT business units of CREDIT SUISSE FIRST BOSTON reserve the =
right to monitor all e-mail communications through its networks. Any views =
expressed in this message are those of the individual sender, except where th=
e=
 message states otherwise and the sender is authorized to state them to be th=
e=
 views of any such entity.
Unless otherwise stated, any pricing information given in this message is =
indicative  only, is subject to change and does not constitute an offer to =
deal at any price quoted. Any reference to the terms of executed transactions=
 =
should be treated as  preliminary only and subject to our formal written =
confirmation.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D