Here is a little more detail from my log files
This is the first delete request:
body =
[
Flex Message (flex.data.messages.DataMessage)
operation = delete
id = ASObject(2486357){subjectid=96}
clientId = 23F55D89-4178-1760-96E1-FF423E27F73C
correlationId = ABF2677D-C583-C966-5B13-FF432FB054B8
destination = subject.destination
messageId = 35CF2AAC-D46C-7E0D-6DFB-FF432FA9A88E
timestamp = 1172513697724
timeToLive = 0
body = SUBJECT[subjectid:96,subjectname:Art]
hdr(DSEndpoint) = my-rtmp,
Flex Message (flex.data.messages.UpdateCollectionMessage)
operation = update_collection
id = null
clientId = null
correlationId = ABF2677D-C583-C966-5B13-FF432FB054B8
destination = subject.destination
messageId = 47C26DFC-113C-824B-F6AE-FF432FA86D76
timestamp = 0
timeToLive = 0
body =
[
[EMAIL PROTECTED](12937429){subjectid=96}]
]
collectionId =
[
]
replace = false
updateMode = client_update
]
And this is the second one: As you can see, there are now 2 objects
queued for deletion:
body =
[
Flex Message (flex.data.messages.DataMessage)
operation = delete
id = ASObject(32142860){subjectid=96}
clientId = 23F55D89-4178-1760-96E1-FF423E27F73C
correlationId = 2B16A7AB-6386-A38D-8C3E-FF43ADE3146B
destination = subject.destination
messageId = 35CF2AAC-D46C-7E0D-6DFB-FF432FA9A88E
timestamp = 1172513730039
timeToLive = 0
body = SUBJECT[subjectid:96,subjectname:Art]
hdr(DSEndpoint) = my-rtmp,
Flex Message (flex.data.messages.DataMessage)
operation = delete
id = ASObject(32250654){subjectid=112}
clientId = 23F55D89-4178-1760-96E1-FF423E27F73C
correlationId = 2B16A7AB-6386-A38D-8C3E-FF43ADE3146B
destination = subject.destination
messageId = 7C9CA1BB-B404-37C4-A3B2-FF43ADE3748E
timestamp = 0
timeToLive = 0
body = SUBJECT[subjectid:112,subjectname:Computer Science],
Flex Message (flex.data.messages.UpdateCollectionMessage)
operation = update_collection
id = null
clientId = null
correlationId = 2B16A7AB-6386-A38D-8C3E-FF43ADE3146B
destination = subject.destination
messageId = 47C26DFC-113C-824B-F6AE-FF432FA86D76
timestamp = 0
timeToLive = 0
body =
[
[EMAIL PROTECTED](32016377){subjectid=96}],
[EMAIL PROTECTED](20392168){subjectid=112}]
]
collectionId =
[
]
replace = false
updateMode = client_update
]
Any ideas on how to clear that previous delete request (which failed
on purpose)?
Thanks
--- In [email protected], "billy_d_white" <[EMAIL PROTECTED]>
wrote:
>
> Maybe Vroom or one of you other FDS experts can tell my what I'm doing
> wrong :
>
> I'm using Cairngorm with a Java/Spring backend. I'm using autocommit
> and autosync enabled and when I perform a deleteItem which I want to
> fail, it calls my Java assembler which attempts the deletion and
> fails. I customize the error message and send it back as a
> MessageException. So far so good.
>
> However, if I then try another deletion, the request is sent to the
> assembler with an array of inside the DataMessage and this array
> contains the previous delete request as well as the new delete
> request. Apparently it is trying to batch the multiple requests since
> the previous one failed. (These are stored in that _token_chain_
> property of the request) How do I avoid this and make each deletion
> request atomic so it will not attempt to execute the previous (failed)
> request? Do I need to re-write the service call on the client to use
> the manual commit() call or something like that?
>
> Any
>
