As most votes preferred solution a) I implemented support for private and protected constructors yesterday. It' already in CVS.
cheers,
Thomas
Thomas Mahler wrote:
hi all, Ganguli Jaideep wrote:Hi all,
Is it absolutely necessary to have a public no argument constructor for
my domain objects?
I have worked with another OR Mapping tool before (Toplink) where this
was not necessary. It still needed a no argument constructor, but the
constructor wasn't required to be public, it could be private.
The main reason to rely on a public constructor was performance. If there is no public constructor you'll have to do some additional reflection magic to make construction possible.
We wanted to keep things simple, thus we also don't have a feature to specify factory classes and methods to construct domain objects.
Let's have a little vote
Do we need support for
a) private no argument constructors?
b) userdefined factories to build domain objects?
cheers,
Thomas
Thanks
Jaideep
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
