Confuse me! The main object is new and the attached ones are not new. The attached entities are absolutely guaranteed to exist and are retrieved using em.find using the same entity manager instance as the main object I am attempting to persist.
I'd love to use build time enhancement, but I put that bugger on hold for now so I can move forward with my coding. I worked around my constant OOM and stack issues with the runtime subclassing enhancer by just throwing heaps of memory at it. I'm a total ANT dummy and the javaagent with OpenEJB on Tomcat 6 I couldn't get working due to conflicts with various commons versions since I use RichFaces. Chris -----Original Message----- From: Daryl Stultz [mailto:[email protected]] Sent: Thursday, 17 September 2009 3:38 AM To: [email protected] Subject: Re: SingleFieldManager crash On Wed, Sep 16, 2009 at 3:31 PM, C N Davies <[email protected]> wrote: > query. I'm wondering why there is no primary key after the hash for > Supplier, I always get it. > > > Not sure about this one, I don't usually see the primary key after the > hash, > I'm using the runtime subclassing enhancement so maybe there is a > difference > there. > > Hmm, any way you can do it with build-time enhancement? Pretty please? > (JPA orm.xml). You cannot attach a reference to a new object without > > cascading. > > Maybe I misread that. I'm reading it as the main object is new and the attachment is an existing entity, not the attached is new... -- Daryl Stultz _____________________________________ 6 Degrees Software and Consulting, Inc. http://www.6degrees.com mailto:[email protected]
