then use a different name/field and treat it like any other field - Don't
>> flag it with @Version.
>>
>> Hope this helps.
>>
>> Andy.
>>
>>
>>
>> -
>> --
>> Andy Gumbrecht
>>
>> http://www.tomitribe.com
>&g
--
> Andy Gumbrecht
>
> http://www.tomitribe.com
> agumbre...@tomitribe.com
> https://twitter.com/AndyGeeDe
>
> TomEE treibt Tomitribe ! | http://tomee.apache.org
> --
> View this message in context:
> http://openejb.979440.n4.nabble.com/OpenJPA-and-DTO-problem-tp4669332p4669334.html
> Sent from the OpenEJB User mailing list archive at Nabble.com.
>
>
> TomEE treibt Tomitribe ! | http://tomee.apache.org
> --
> View this message in context:
> http://openejb.979440.n4.nabble.com/OpenJPA-and-DTO-problem-tp4669332p4669334.html
> Sent from the OpenEJB User mailing list archive at Nabble.com.
t Tomitribe ! | http://tomee.apache.org
--
View this message in context:
http://openejb.979440.n4.nabble.com/OpenJPA-and-DTO-problem-tp4669332p4669334.html
Sent from the OpenEJB User mailing list archive at Nabble.com.
Hi
does it happen if you don't do it for the else case (new Fact())? But
I guess it is linked to a relationship maybe
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2014-05-
Hi,
I use openjpa with DTO and when I try to manage @Version I get an
exception: Detected attempt to modify field
"com.kildeen.ref.domain.BaseEntity.version" with value strategy "restrict".
What I do is, I use find if the DTO has id. I then copy back the version
field but it seems It does not wo
