ive JPA (EclipseLink)
> and then the same scenario with DS Data... and looking for different
> outcomes.
>
> Bottom line? I agree with John that this discussion needs attention.
>
> More to come,
> Marvin
>
> -Original Message-
> From: John D. Amen
, 2015 5:22 PM
To: dev@deltaspike.apache.org; Marvin Toll
Subject: Re: Issues with EntityRepository.save()
So the discussions on this died down, but I think we should still plan to do
something regarding the issue.
I'd like to propose that we do #1 and the back half of #4.
We may want to ad
>> Sounds good... perhaps obviously I'm a DeltaSpike newbie and negotiating
> >> my way through the learning curve.
> >>
> >> -Original Message-----
> >> From: Karl Kildén [mailto:karl.kil...@gmail.com]
> >> Sent: Friday, August 14, 2015 8:00
Kildén [mailto:karl.kil...@gmail.com]
>> Sent: Friday, August 14, 2015 8:00 AM
>> To: dev@deltaspike.apache.org; marvint...@gtcgroup.com
>> Subject: Re: Issues with EntityRepository.save()
>>
>> Marvin,
>>
>> What you are suggesting is not required imo.
aps obviously I'm a DeltaSpike newbie and negotiating
> my way through the learning curve.
>
> -Original Message-
> From: Karl Kildén [mailto:karl.kil...@gmail.com]
> Sent: Friday, August 14, 2015 8:00 AM
> To: dev@deltaspike.apache.org; marvint...@gtcgroup.com
t: Re: Issues with EntityRepository.save()
Marvin,
What you are suggesting is not required imo. Some strategy configuration like
suggested from Thomas would give the same benefits.
On 14 August 2015 at 13:39, Marvin Toll wrote:
> At the moment, I don't see a way to specify and implement
gmail.com]
> Sent: Friday, August 14, 2015 5:00 AM
> To: dev@deltaspike.apache.org; marvint...@gtcgroup.com
> Subject: Re: Issues with EntityRepository.save()
>
> Thanks guys for all the effort in digging into the issue here. From a
> pragmatic point of view I guess #2 would be my preferred
g; marvint...@gtcgroup.com
Subject: Re: Issues with EntityRepository.save()
Thanks guys for all the effort in digging into the issue here. From a pragmatic
point of view I guess #2 would be my preferred option and then think about what
we should do with that save thing :) Maybe a strategy pattern similar t
---
> From: Harald Wellmann [mailto:hwellmann...@gmail.com]
> Sent: Wednesday, August 12, 2015 5:46 PM
> To: dev@deltaspike.apache.org
> Subject: Issues with EntityRepository.save()
>
> This is a quick summary of the issues around EntityRepository.save() that
> seem to exist since
tion for a Data2
module? One that does not try to mirror Spring (or the Repository Pattern) but
rather seeks to extend the JPA2 API?
_Marvin
-Original Message-
From: Harald Wellmann [mailto:hwellmann...@gmail.com]
Sent: Wednesday, August 12, 2015 5:46 PM
To: dev@deltasp
This is a quick summary of the issues around EntityRepository.save()
that seem to exist since 1.4.2.
I'll create test cases and JIRA issues as time permits, but I think
these notes may be helpful at this stage to find out whether or not
incompatibilities experienced by other users have the sam
11 matches
Mail list logo