deleting

Suppose a context owns a certain aggregate and another uses it. Now the owning context is suppose to remove the aggregate and within its own context has no problem doing so. But the other context can agree with the removing of the aggrgate. An example would be some client administration context and an invoice context. The client may be removed, but as long as there are unpaid invoices, or even invoices to be created, the invoice context simply can handle a removed client.

The question is; is there any good way to handle the setup without using distributed transactions (JMS with JTA/XA) and also without manually keeping track of acknowledgements that other contexts need to send before a client can be deleted?

Tom




------------------------------------