Glad you were able to sort it out. An addition to the docs would be great! I believe the docs for the data module are currently the README in the git repo. Care to create a patch, or simply add them here via email? At the very least, please create a ticket so we don't forget to document this.
Real usage like this helps us make DeltaSpike better and easier to use. Thank you very much for helping us out! — Sent from Mailbox for iPhone On Fri, Dec 27, 2013 at 10:32 PM, Walter White <[email protected]> wrote: > It looks like glassfish and arquillian are correct, it appears to be an > issue with .equals and .hashCode. I found this out by starting from > scratch without a custom implementation for .equals and .hashCode which is > what eclipselink uses to determine if the entity is the same or not. This > might be a good item for the FAQ or at least my FAQ. > Thanks, > Walter > On Fri, Dec 27, 2013 at 4:43 PM, Walter White > <[email protected]>wrote: >> Ok, I'll try that after I check my configuration. I will update/check >> persistence.xml to ensure it is properly configured, then test with >> arquillian. >> >> >> On Fri, Dec 27, 2013 at 4:40 PM, Jason Porter <[email protected]>wrote: >> >>> Can you recreate with an Arquillian test to see if it's just glassfish?— >>> Sent from Mailbox for iPhone >>> >>> On Fri, Dec 27, 2013 at 1:35 PM, Walter White >>> <[email protected]> wrote: >>> >>> > Hi, >>> > I am having issues when using the deltaspike data module to persist >>> > entities: >>> > >>> http://stackoverflow.com/questions/20722811/apache-delta-spike-queryinvocationcontext >>> > I am using glassfish with JTA, with parent-child relationships, it >>> appears >>> > it will attempt to insert 2 entities which results in a constraint >>> error. >>> > I confirmed the duplicate inserts via wireshark and can confirm 2 insert >>> > statements are sent. >>> > I'm hoping for some direction, perhaps it is a configuration issue. >>> > Walter >>> >> >>
