Anyone is using NSITYBus 2.0 successfully with Integration 2.0?
I have tried to compile the sources of NServiceBus.ObjectBuilder.Unity.dll against the Unity 2.0 assembly, but due to the change / deletion of many object methods in the new Unity, many compile-time errors found.
The 5 methods of IContainer are easy to implement in any document containing any container but when I look into the implementation of NServiceBus.ObjectBuilder.Unity, I suppose That's a lot to be done. Why is it like this?
Unity, by default, behaves differently from NSB's expectations. This is the reason that some custom extensions are required to be compatible with the objectbilder contract. There are two main differences:
- Unity is needed to inject dependency into the property. NSB expects the objectbuilder to be injected into any asset which
- while assessing property, the unity considers property dependence as mandatory while NSB is expected to be optional.
I believe these features are preserved in version 2.0 and they will be easy to move. I should be here sometime this week and I hope that I will be implementing the Unity v2 implementation.
EDIT: The completed Unit 2 object builder is in the trunk.
Comments
Post a Comment