I know it's impossible, but I gotta come up with something... webservices rule in the apps we use for interop between system AND (and this is the kicker for us) internally in one core app as it passes data around it's subsystems (this core app was not built by us)
we have to publish child/parent/grandparent data to the core system from other apps. For the sake of sanity, we roll up this data into one job lot and publish as one action. what we've found out is the workflow within the core app then uses descrete webservices within itself to update the child, parent, grandparent data as descrete CRUD webservices. from what we can tell, there is no way to recover and roll back any changes if one of the CRUD webservice operations fail. We can get inside the workflow to add custom code around each webservice call, but we can't get to the target of the webservices (which has - from what we can gather - convoluted authentication tightly integrated with Active Directory and other modifiers to stop us from simply inserting into it's database). the only thing I can think of (apart from trying to duplicate what it would take to insert directly into the database bypassing the webservices) is to apply something like a memento pattern to roll back to it's pre-updated states if any of the internal webservice calls fail. The downside to that (at a guess) is that it's susceptable to data collision when two actions are editing the same set (or part) of records. anyone else come across a nasty situation like this? any suggestions? many thanx barry.b --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CFCDev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cfcdev?hl=en -~----------~----~----~----~------~----~------~--~---
