Isn't that what constructors are for?
On 2/11/07, Clinton Begin <[EMAIL PROTECTED]> wrote:
Absolutely not. :-)
Direct field mapping for the purposes of immutable classes or non-bean
types would be pointless. So yes, we're completely ignoring private
on fields, setters, and constructors.
I do
Yes, you're absolutely right about that. Constructor injection is our
goal going forward. It's quite a bit harder to implement than direct
field mapping, but I would like to see it. I may look into it next
week.
Direct field is still important though, for people that don't buy into
constructor
The votes are in an iBATIS for Java version 2.3.0 is declared to be Apache
general availability status.
This release is the first release that does not include the DAO framework.
The DAO framework is available as a separate download on the Java downloads
page, but we recommend migrating to Spring
okay
On 2/11/07, Clinton Begin <[EMAIL PROTECTED]> wrote:
Yes, you're absolutely right about that. Constructor injection is our
goal going forward. It's quite a bit harder to implement than direct
field mapping, but I would like to see it. I may look into it next
week.
Direct field is still
