RE: WithMultiArgsConstructor

[Richard Beauchamp <ri...@rbeau.com>]

Hello all,

I know this is a reply to an old post, but I'm just now updating our
infrastructure from OJB 0.9 to 0.9.8 and noticed that the new
'buildWithMultiArgsConstructor' method signature is modified (i.e., declares
a Map rather than an Object[]) and is not used anymore.

Having a safe 'buildWithMultiArgsConstructor' (as in OJB 0.9) is extremely
important to our team because we declare some persistent object (po)
properties as 'final'. If the only means to create a po was via a no-arg
constructor + reflection (as in OJB 0.9.8) then we couldn't declare some po
properties as 'final' and our pos would therefore become less correct and
less safe.

I'll work on a safe 'buildWithMultiArgsConstructor' and post it to the OJB
dev list.

Cheers,

Richard




> From: Mahler Thomas thomas.mahler@itellium.com>
> Subject: AW: WithMultiArgsConstructor
> Date: Tue, 9 Jul 2002 17:17:25 +0200
> Hi,

> > -----Ursprüngliche Nachricht-----
> > Von: Matthew Baird [mailto:Matthew.Baird@motiva.com]
> > Gesendet: Montag, 8. Juli 2002 23:54
> > An: OJB Developers List
> > Betreff: RE: WithMultiArgsConstructor
> >
> >
> > I think I took out the buildWithMultiArgsConstructor
> > functionality as it is pretty dangerous. I left this function
> > in case anyone complained.
> >
> > I will remove it if no one minds.
>
> Please not remove it!
>
> I think we should reimplement the buildWithMultiArgsConstructor in a safe
> way.
> Using this constructor is much faster than setting the primitive type
> attributes one by one.
>
> cheers,
> Thomas