Just thought I might add to the conversation. I've started prototyping an implementation for future RabbitMQ support.
So far the IOneWayBus is in with IMessageBuilder implemented. Currently working on ISubscriptionStorage and ITransport implementations. I'm still trying to wrap my head around how the internals exactly work and I'm doing a lot of cross referencing and adapting from MSMQ. At the moment I've made RabbitMQ a dependency, it will need to be broken off into a separate package as per the strategy with RhinoQueues. I'll keep you updated. On Friday, 17 August 2012 07:08:04 UTC+10, Corey wrote: > > Shouldn't be a problem to get it in. Sounds like we will also be breaking > out the dependency on RhinoQueues into a separate nuget package. > > On Thu, Aug 16, 2012 at 2:59 PM, Jakub Berezanski > <ku...@berezanscy.pl<javascript:> > > wrote: > >> Speaking of container updates, I've sent a pull request ( >> https://github.com/hibernating-rhinos/rhino-esb/pull/56) with Windsor >> updated to 3.1. It would be nice if this made it into the release - I would >> like to use the newest Windsor in my apps and I don't like binding >> redirects. >> >> On Monday, August 13, 2012 6:04:06 PM UTC+2, Corey wrote: >> >>> Honestly, I'm fine with whatever solution you choose. I don't have a >>> large stake in Spring support, so I don't know if my opinion matters. >>> >>> On Sat, Aug 11, 2012 at 9:07 AM, Marko Lahma <marko...@gmail.com> wrote: >>> >>>> >>>> I investigated the matter shortly last weekend (other things came to >>>> take some time) and we have two options: >>>> >>>> * Plain assembly redirect (easy and quick, requires users the to know >>>> about it) >>>> * Use Spring.NET 2.0 *nightly build*, M1 release hasn't for some reason >>>> signed dlls so they won't work with current requirements >>>> >>>> Going for 3.x release a new and shine Spring.NET 2.0 sounds good, but >>>> will require users to use "experimental" (though it's solid). >>>> >>>> What would be the path to take? >>>> >>>> -Marko >>>> >>>> >>>> On Friday, August 10, 2012 11:11:28 PM UTC+3, Corey wrote: >>>> >>>>> One quick update. Ryan was able to get some of the capabilities for >>>>> delivery options DeliverBy, and MaxAttempts into the MsmqTransport. With >>>>> the caveat that MaxAttempts must be one if used. >>>>> >>>>> Marko, any progress on your end? >>>>> >>>>> On Sat, Aug 4, 2012 at 1:05 PM, Marko Lahma <marko...@gmail.com>wrote: >>>>> >>>>>> >>>>>> >>>>>> I'll have a look wrt Spring problems. Hopefully tomorrow (Sunday). >>>>>> Latest Common.Logging is always the best option but need to check >>>>>> whether >>>>>> to use binding redirects or upgrade to Spring.NET 2.0 M1.. >>>>>> >>>>>> -Marko >>>>>> >>>>>> >>>>>> On Saturday, August 4, 2012 12:15:47 AM UTC+3, Corey wrote: >>>>>>> >>>>>>> -The changes for Rhino.Queues sending options have been pulled in. >>>>>>> -- Maximum retry count on send failure >>>>>>> -- Deliver by, if time is exceeded the message is discarded >>>>>>> -Removal of log4net in favor of Common.Logging >>>>>>> -Pulled in spelling error. >>>>>>> >>>>>>> Ryan is looking into whether or not some or all of the sending >>>>>>> options will work with the MSMQ transport as well. >>>>>>> >>>>>>> Spring tests are not passing due to version conflict (I chose 2.1.1) >>>>>>> Marko, are you up for this or would a different version be better? >>>>>>> >>>>>>> We will begin to incorporate these changes into our environment over >>>>>>> the next week or two. Provided things are running smooth I will publish >>>>>>> to >>>>>>> nuget then. >>>>>>> >>>>>> -- >>>>>> You received this message because you are subscribed to the Google >>>>>> Groups "Rhino Tools Dev" group. >>>>>> To view this discussion on the web visit https://groups.google.com/d/ >>>>>> **ms**g/rhino-tools-dev/-/5-**eRWeybbJ**YJ<https://groups.google.com/d/msg/rhino-tools-dev/-/5-eRWeybbJYJ> >>>>>> . >>>>>> To post to this group, send email to rhino-t...@googlegroups.**com. >>>>>> To unsubscribe from this group, send email to rhino-tools-d...@** >>>>>> googlegroups.**com. >>>>>> >>>>>> For more options, visit this group at http://groups.google.com/** >>>>>> group**/rhino-tools-dev?hl=en<http://groups.google.com/group/rhino-tools-dev?hl=en> >>>>>> . >>>>>> >>>>> >>>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "Rhino Tools Dev" group. >>>> To view this discussion on the web visit https://groups.google.com/d/** >>>> msg/rhino-tools-dev/-/**shcEsaE3g-EJ<https://groups.google.com/d/msg/rhino-tools-dev/-/shcEsaE3g-EJ> >>>> . >>>> >>>> To post to this group, send email to rhino-t...@googlegroups.**com. >>>> To unsubscribe from this group, send email to rhino-tools-d...@** >>>> googlegroups.com. >>>> For more options, visit this group at http://groups.google.com/** >>>> group/rhino-tools-dev?hl=en<http://groups.google.com/group/rhino-tools-dev?hl=en> >>>> . >>>> >>> >>> -- >> You received this message because you are subscribed to the Google Groups >> "Rhino Tools Dev" group. >> To view this discussion on the web visit >> https://groups.google.com/d/msg/rhino-tools-dev/-/a74fHX88GOkJ. >> >> To post to this group, send email to rhino-t...@googlegroups.com<javascript:> >> . >> To unsubscribe from this group, send email to >> rhino-tools-d...@googlegroups.com <javascript:>. >> For more options, visit this group at >> http://groups.google.com/group/rhino-tools-dev?hl=en. >> > > -- You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To view this discussion on the web visit https://groups.google.com/d/msg/rhino-tools-dev/-/X7-ClMAvQ2wJ. To post to this group, send email to rhino-tools-dev@googlegroups.com. To unsubscribe from this group, send email to rhino-tools-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en.
