RE: [flexcoders] FDS with Java Question: Why is it grouping requests?

2007-02-27 Thread Jeff Vroom 
When you get the fault for the first delete, you probably just need to
call revertChanges - either for all changes or just that item.   After
any fault, all messages you commit as part of that batch get reverted -
i.e. put back into the uncommitted list.  When you revert them, we'll
undo those changes - i.e. recreate the deleted item.  This is necessary
to keep the client's view of the managed state in sync with the server's
view.

 

Jeff

 



From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of billy_d_white
Sent: Monday, February 26, 2007 9:52 AM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] FDS with Java Question: Why is it grouping
requests?

 

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

[flexcoders] FDS with Java Question: Why is it grouping requests?

2007-02-26 Thread billy_d_white 
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

RE: [flexcoders] FDS with Java Question: Why is it grouping requests?

2007-02-26 Thread Dimitrios Gianninas 
Maybe u need to call revertchanges() after the fault occurs to put everything 
back the way it was and then allow the user to delete the other record of his 
choosing.
 
Dimitrios Gianninas
RIA Developer
Optimal Payments Inc.
 



From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of 
billy_d_white
Sent: Monday, February 26, 2007 12:52 PM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] FDS with Java Question: Why is it grouping requests?



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



 

-- 
WARNING
---
This electronic message and its attachments may contain confidential, 
proprietary or legally privileged information, which is solely for the use of 
the intended recipient.  No privilege or other rights are waived by any 
unintended transmission or unauthorized retransmission of this message.  If you 
are not the intended recipient of this message, or if you have received it in 
error, you should immediately stop reading this message and delete it and all 
attachments from your system.  The reading, distribution, copying or other use 
of this message or its attachments by unintended recipients is unauthorized and 
may be unlawful.  If you have received this e-mail in error, please notify the 
sender.

AVIS IMPORTANT
--
Ce message électronique et ses pièces jointes peuvent contenir des 
renseignements confidentiels, exclusifs ou légalement privilégiés destinés au 
seul usage du destinataire visé.  L'expéditeur original ne renonce à aucun 
privilège ou à aucun autre droit si le présent message a été transmis 
involontairement ou s'il est retransmis sans son autorisation.  Si vous n'êtes 
pas le destinataire visé du présent message ou si vous l'avez reçu par erreur, 
veuillez cesser immédiatement de le lire et le supprimer, ainsi que toutes ses 
pièces jointes, de votre système.  La lecture, la distribution, la copie ou 
tout autre usage du présent message ou de ses pièces jointes par des personnes 
autres que le destinataire visé ne sont pas autorisés et pourraient être 
illégaux.  Si vous avez reçu ce courrier électronique par erreur, veuillez en 
aviser l'expéditeur.