Mailing-List: contact user-help@cayenne.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cayenne.apache.org
MIME-Version: 1.0
In-Reply-To: <A07136BA-40C4-46E2-9BAD-F2FCFFDDF7A0@selbstdenker.ag>
References: <93685978-CF98-447B-AA64-D447116E9451@godurkodi.is>
 <2F0E894D9C1C4E45B3128748AAD0C049@IV5> <59917604-F39B-493D-80BF-370697EE5244@godurkodi.is>
 <52F57598-3432-46B9-B7B3-6D7F9D6E1458@swarmbox.com> <A07136BA-40C4-46E2-9BAD-F2FCFFDDF7A0@selbstdenker.ag>
From: Michael Gentry <blacknext@gmail.com>
Date: Wed, 1 Mar 2017 14:31:29 -0500
Message-ID: <CAOy5kzP+zWCUmTOrGRZJK8=6FCTo73DVZnytfdDqcGr39A7_TA@mail.gmail.com>
Subject: Re: Validation and @PrePersist
To: Cayenne Users <user@cayenne.apache.org>
Content-Type: multipart/alternative; boundary=f403045f83f6c3773e0549b05d84
archived-at: Wed, 01 Mar 2017 19:32:09 -0000

--f403045f83f6c3773e0549b05d84
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Maik,

I've historically done data manipulations in the lifecycle events
(pre-persist, post-add, post-load, etc) and not the validate methods.  I
kind of agree with you that validate shouldn't be modifying data.  I'm
hoping someone else explains the change now.  :-)

mrg


On Wed, Mar 1, 2017 at 11:43 AM, Musall, Maik <maik@selbstdenker.ag> wrote:

> Hi all,
>
> but isn't hte purpose of validation to check if the object to be saved is
> in a valid state? That would imply that validation has a positive (pass) =
or
> negative (ValidationException) result, and no side effects. Modifying the
> object during validation would defeat the purpose, wouldn't it?
>
> Maik
>
> > Am 01.03.2017 um 17:12 schrieb Matt Watson <matt@swarmbox.com>:
> >
> > When I ran into this same scenario I realized that =E2=80=9CvalidateFor=
Insert=E2=80=9D
> was the hook I needed, instead of @PrePersist.
> >
> > @Override
> > public void validateForInsert(ValidationResult validationResult) {
> >       if (getReference() =3D=3D null || getReference().isEmpty()) {
> >               setReference(System.getNextPurchaseOrderReference());
> >       }
> >       super.validateForInsert(validationResult);
> > }
> >
> >
> >
> >> On Mar 1, 2017, at 5:51 AM, Hugi Thordarson <hugi@godurkodi.is> wrote:
> >>
> >> Hi Jurgen,
> >> fine suggestion but unfortunately not the part of the lifecycle I need
> to catch=E2=80=94the action needs to be performed before committing, not =
after
> adding (so basically I need @PrePersist=E2=80=94but I need it before vali=
dation
> happens).
> >>
> >> Cheers,
> >> - hugi
> >>
> >>
> >>> On 1. mar. 2017, at 13:14, <dollj@xsinet.co.za> <dollj@xsinet.co.za>
> wrote:
> >>>
> >>> Hi Hugi
> >>>
> >>> For this kind of thing use @PostAdd instead.
> >>>
> >>> Regards
> >>> Jurgen
> >>>
> >>>
> >>> -----Original Message----- From: Hugi Thordarson
> >>> Sent: Wednesday, March 1, 2017 1:18 PM
> >>> To: user@cayenne.apache.org
> >>> Subject: Validation and @PrePersist
> >>>
> >>> Hi all,
> >>> I have some logic in a Listener that uses @PrePersist to populate the
> value of a required attribute before committing changes. Turns out this
> doesn=E2=80=99t work, since Cayenne invokes validateForInsert() before ru=
nning
> @PrePersist.
> >>>
> >>> Any suggestions for where I can invoke logic populates required value=
s
> before validation?
> >>>
> >>> Cheers,
> >>> - hugi
> >>
> >
>
>

--f403045f83f6c3773e0549b05d84--