如何解决与 NHibernateSagaPersister 的自动装配冲突？

发布于 2024-11-19 13:17:27 字数 1284 浏览 1 评论 0原文

我正在尝试连接我的第一个 Saga，但无法让接收端点正确处理启动消息。我得到以下异常：

SagaMessageHandler 处理失败信息。 Spring.Objects.Factory.UnsatisfiedDependencyException：使用名称创建对象时出错 'NServiceBus.Sagas.Impl.SagaMessageHandler' ：表达出未满足的依赖性通过对象属性“Persister”：有 2 个 Type 对象 [NServiceBus.Saga.ISagaPersister] 为按类型自动装配，当需要时已经只有 1 能够 autowire 属性 'Persister' of 目的 'NServiceBus.Sagas.Impl.SagaMessageHandler'。

我猜测内存持久程序和 NHibernateSagaPersister 都存在冲突，但我不知道如何解决这个问题。我的配置是这样的：

public class SubscriberEndpointConfig : IWantCustomInitialization, IConfigureThisEndpoint
{      
    public void Init()
    {
        _logger.Info("Subscriber is initializing..");

        Configure.With()                 
            .DefaultBuilder()
            .XmlSerializer()
            .MsmqTransport().IsTransactional(true).IsolationLevel(IsolationLevel.ReadCommitted).PurgeOnStartup(false)
            .UnicastBus().LoadMessageHandlers(First<GridInterceptingMessageHandler>.Then<SagaMessageHandler>())  
            .Sagas()
            .NHibernateSagaPersister()
            .Log4Net();

    }
}

如果我删除 LoadMessageHandlers()，错误就会消失，但当然我的处理程序永远不会被调用。有什么想法这里出了什么问题吗？当我在生产配置文件中使用 AsA_Server 时，传奇可以正常工作，无需自定义初始化，但由于其他原因我需要使用它。

原文

I'm trying to wire up my first Saga, and have been unable to get the receiving endpoint to handle start message properly. I get the following exception:

SagaMessageHandler Failed handling
message.
Spring.Objects.Factory.UnsatisfiedDependencyException:
Error creating object with name
'NServiceBus.Sagas.Impl.SagaMessageHandler'
: Unsatisfied dependency expressed
through object property 'Persister':
There are 2 objects of Type
[NServiceBus.Saga.ISagaPersister] for
autowire by type, when there should
have been just 1 to be able to
autowire property 'Persister' of
object
'NServiceBus.Sagas.Impl.SagaMessageHandler'.

I'm guessing that both the in-memory persister and NHibernateSagaPersister are conflicting, but I can't figure out how to resolve this. My configuration is this:

public class SubscriberEndpointConfig : IWantCustomInitialization, IConfigureThisEndpoint
{      
    public void Init()
    {
        _logger.Info("Subscriber is initializing..");

        Configure.With()                 
            .DefaultBuilder()
            .XmlSerializer()
            .MsmqTransport().IsTransactional(true).IsolationLevel(IsolationLevel.ReadCommitted).PurgeOnStartup(false)
            .UnicastBus().LoadMessageHandlers(First<GridInterceptingMessageHandler>.Then<SagaMessageHandler>())  
            .Sagas()
            .NHibernateSagaPersister()
            .Log4Net();

    }
}

If I remove the LoadMessageHandlers(), the error disappears but of course my handler is never invoked. Any ideas what's wrong here? The saga works properly when I am using AsA_Server in the production profile, without the custom initialization, but I need to use that for other reasons.

分享到QQ

分享到微博