I ran into this as well and this solution worked. Would it make sense to add a model validation that would look for the condition and generate an error? Does the problem arise when referencing an aggregate root without cascade="none"?
Patrik Nordwall wrote: > > I think the solution for this problem is to use cascade="none" for the > item reference in SequencedItem. > > ValueObject SequencedItem { > - @ItemSet itemSet <-> seqItems > Integer sequence range="min=1" > - @Item item cascade="none" > } > > /Patrik > > -- View this message in context: http://old.nabble.com/-Sculptor--detached-entity-passed-to-persist--tp27648394s17564p28056704.html Sent from the Fornax-Platform mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Fornax-developer mailing list Fornax-developer@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fornax-developer