Updating a property on a saga outside of the saga

Question

I need to perform edits on my saga documents outside of the saga. I am trying to do the simple property update which is:

                SaleSaga saga = session.Load<SaleSaga>(id);
                saga.SaleSagaTaskId = taskId;
                session.SaveChanges();

This does not work, I end up with this issue.

    {"Entity Messages.SaleSaga had document key 'salesaga/d6b639c4-78a1-4be6-8e44-a283010b11a9' 
but now has document key property 'salesagas/d6b639c4-78a1-4be6-8e44-a283010b11a9'
.\r\nYou cannot change the document key property of a entity loaded into the session"}

I am not sure why it is adding an 's' on to the end of "salesagas". I'm at a loss as to the best way to resolve this, any help would be greatly appreciated.

EDIT: This is for an NServiceBus saga and the error is occurring when attempting to save the edited document back to RavenDB.

I tried doing patching, but I was ending up with some kind of URL: "\bulk_docs" error with Newtonsoft Json serializer. — MattB, Dec 03 '13 at 21:59
Sorry, this is an NServiceBus saga, and the error is happening when trying to edit the document from the RavenDB. — MattB, Dec 04 '13 at 15:42

score 3 · Accepted Answer · answered Dec 04 '13 at 16:26

The NServiceBus Saga Persister uses different conventions for storing sagas than the Raven default conventions. The Raven default convention is to take the class name and pluralize it. Apparently NServiceBus does not do so. So you have a mismatch by accessing the data in fundamentally different ways.

You may want to reuse the NServiceBus Saga Persister class. The Saga persistence code can be found here:

https://github.com/Particular/NServiceBus/tree/4.2.0/src/NServiceBus.Core/Persistence/Raven

score 0 · Answer 2 · answered Dec 03 '13 at 23:26

0

How was the original object written? It looks to me like the reader and writer of this data might be two different systems, or two different versions of this system, and the the document conventions have changed.

Either use the original convention, or use a string identifier instead of a Guid.

answered Dec 03 '13 at 23:26

Matt Johnson-Pint

230,703
74
448
575

I guess I'm not sure what you're asking. We are changing identifiers on the sagas and this is the reason for editing the saga outside of the saga handler. It is occurring within the same namespace, what I'm trying to solve is why it is changing the original document path from 'SaleSaga' to 'SaleSagas' – MattB Dec 04 '13 at 13:07

Updating a property on a saga outside of the saga

2 Answers2