agree with John that this discussion needs attention.
More to come,
Marvin
-Original Message-
From: John D. Ament [mailto:johndam...@apache.org]
Sent: Friday, August 21, 2015 5:22 PM
To: dev@deltaspike.apache.org; Marvin Toll marvint...@gtcgroup.com
Subject: Re: Issues
.
-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
Subject: Re: Issues with EntityRepository.save()
Marvin,
What you are suggesting is not required imo. Some
: 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 add some additional comments. For example, recommend that the
@Id
: 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 option and then think about what
: 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 marvint...@gtcgroup.com wrote:
Harald At the moment, I don't see a way to specify
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 AM
To: dev@deltaspike.apache.org; marvint...@gtcgroup.com
Subject: Re: Issues
@deltaspike.apache.org
Subject: Issues with EntityRepository.save()
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
...@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
with EntityRepository.save()
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
