Yeah, I'd recommend turning off auto-commit. It makes this type of thing a little harder and a little slower. When you create a new item and then commit immediately, we have to wait for that first commit to complete so we get the id before we can even send the update to the item to refer to it. If you do them both in the same batch, we can do that all in one round-trip.
I've been meaning to add a new auto-commit mode where we just do the commit in a "call later" type of function. This would still give you the simplicity of coding with auto-commit but would automatically batch changes made in the same frame. You could also just do that yourself is you register for "enter frame" events. Just call commit if "commit required" is set to true. The Message.* and Service.Data.* targets give the best diagnostics. If you want to reduce the amount of log output, you can just turn on debug logging just before you do the operation. I think I sent you that logger.jsp which does that. Once you get the logs, you'll see the batched message which contains all of the changes in the batch in the "body" of the batched message. The debug logs print out that batched message before and after the transaction. In between, the Service.Data.* targets will show you the individual operations as they are handed to the assembler. Jeff ________________________________ From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Sent: Tuesday, March 04, 2008 2:23 AM To: flexcoders@yahoogroups.com Subject: [flexcoders] Re: LCDS Error?? Now that I know where to look I'll look at the code and see how this is being committed. We do have auto commit on which brings up a good question. Is auto commit dangerous? I have talked to some other coders who say they never use it and I am wondering if we should move towards a more manual committing structure to avoid these kinds of possible problems. The error I pasted in the post is all that showed up in the log for this transaction although I have turned off some of my logging output to try to reduce the size of my logs. Which log should I re-enable to send you the info you need? Is there a way to see what operations are sent with each batch transaction? - Kevin --- In flexcoders@yahoogroups.com <mailto:flexcoders%40yahoogroups.com> , "Jeff Vroom" <[EMAIL PROTECTED]> wrote: > > It sounds like somehow those changes are being split into two different > batches. Do you perhaps have auto-commit on or are you calling commit > in the middle? > > > > There was a bug in 2.5.1 where this error was printed sometimes but I > don't think I've seen a case where it caused any problems. If you have > the server debug log for this case though I'd be glad to try and figure > out why that change is not getting saved in this case. > > > > Jeff > > > > ________________________________ > > From: flexcoders@yahoogroups.com <mailto:flexcoders%40yahoogroups.com> [mailto:flexcoders@yahoogroups.com <mailto:flexcoders%40yahoogroups.com> ] On > Behalf Of Kevin > Sent: Monday, March 03, 2008 1:18 PM > To: flexcoders@yahoogroups.com <mailto:flexcoders%40yahoogroups.com> > Subject: [flexcoders] LCDS Error?? > > > > Has anyone gotten this error in LCDS before? I can't seem to figure > out what it means and what to do about it. > > [Flex] 03/03/2008 18:59:12.466 [ERROR] [Service.Data.General] Can't > find create message for newly created item with message id: > EB473A3B-AF5D-1E26-7831-7600782E18C5 > > I couldn't find anything in google as well. The error was being > thrown when a user tried to commit a nested object for persistence. > > (Such as a new UserVO which contains a new ContactVO as a property) > > I this case the UserVO persisted correctly and the ContactVO > persisted, but the ContactVO id did not save correctly in the users > table and then the user.contact property was null. > > Any thoughts? - Kevin >
