StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POManaging RavenDb session in Windsor under NServiceBus
primarykey
Id
11774386
data
AcceptedAnswerId
0
AnswerCount
3
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2012-08-02T09:11:44.367
FavoriteCount
2
LastActivityDate
2013-01-29T13:12:16.017
LastEditDate
2012-08-08T11:36:14.293
LastEditorUserId
6980
OwnerUserId
6980
ParentId
0
PostTypeId
1
Score
5
ViewCount
797
LastEditorDisplayName
text
Body
I'm using NServiceBus (3.2.2), RavenDB (1.2.2017-Unstable) and Windsor (3.0.0.4001) in an MVC 4 project. I have a IHandleMessages class that handles 3 different messages, and that needs an IDocumentSession, and therefore defines a property such as: <pre><code>public IDocumentSession DocumentSession { get; set; } </code></pre> I've copied the RavenDbUnitOfWork implementation from NServiceBus' <a href="http://nservicebus.com/UnitOfWorkImplementationForRavenDB.aspx" rel="noreferrer">website</a> I've registered IDocumentStore, IDocumentSession and IManageUnitsOfWork in my Windsor container as follow: <pre><code>container.Register( Component .For<IManageUnitsOfWork>() .ImplementedBy<RavenUnitOfWork>() .LifestyleTransient() ); container.Register( Component .For<IDocumentStore>() .UsingFactoryMethod(k => DocumentStoreHolder.DocumentStore) .LifestyleSingleton(), Component .For<IDocumentSession>() .UsingFactoryMethod(k => k.Resolve<IDocumentStore>().OpenSession()) .LifestyleTransient() ); </code></pre> NServiceBus is configured to use my container: <pre><code>Configure.With() .CastleWindsorBuilder(container); </code></pre> I'm encountering the problem that the UnitOfWork and the message handler receive different instances of the DocumentSession. This means that objects stored in the session in the message handler are not saved, since SaveChanges() is called on a different DocumentSession. Removing the Transient lifestyle causes different kind of problems, that result in concurrency/conflicts when updating objects from RavenDb, since (probably) the message handler keeps getting the same instance of the DocumentSession, which holds a cached version of the updated object. Update: As suggested, I've tried changing the registration of the IDocumentSession in Windsor, to the Scope lifestyle, like this: <pre><code>Component .For<IDocumentSession>() .UsingFactoryMethod(k => k.Resolve<IDocumentStore>().OpenSession()) .LifestyleScope() </code></pre> This causes exceptions when the container tries to resolve the MVC Controller, saying that the scope was not found, and asking if I forgot to call BeginScope().
Tags
<castle-windsor><nservicebus><ravendb>
Title
Managing RavenDb session in Windsor under NServiceBus
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USSaguiItay
UserOwnerUserId
1. USSaguiItay
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
3. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
CommentsPostId
1. COCan you add the definition to DocumentStoreHolder?
 singulars
 PostPostId
 POManaging RavenDb session in Windsor under NServiceBus
 UserUserId
 USAdam Fyles

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.