No, because discarded messages are for _arriving_ messages. On Mon, Jan 19, 2009 at 2:43 PM, chrisortman <[email protected]> wrote:
> > Currently when doing IServiceBus.Notify(message) nothing happens if > there are no subscribers. > Should this also generate a discarded message? > > On Jan 19, 11:04 am, Ayende Rahien <[email protected]> wrote: > > That is an extremely common approach. > > For that matter, here is the real configuration behind the NH Prof > website: > > > > <castle> > > > > <facilities> > > > > <facility id="rhino.esb" > > > > > <bus threadCount="1" > > > > numberOfRetries="5" > > > > endpoint="msmq://localhost/nhprof.backend" > > > > /> > > > > <messages> > > > > <add name="NHProfilerWeb.Backend.InternalMessages" > > > > endpoint="msmq://localhost/nhprof.backend"/> > > > > <add name="NHProfilerWeb.Messages" > > > > endpoint="msmq://localhost/nhprof.backend"/> > > > > </messages> > > > > </facility> > > > > </facilities> > > > > On Mon, Jan 19, 2009 at 12:00 PM, chrisortman <[email protected]> > wrote: > > > > > Does it violate anything if the same bus that sends the message is > > > also the one that is watching that queue? > > > > > Lets say I have 2 apps. > > > 1 NHProf website > > > 2 Windows Service that does order processing > > > > > So in the web app I would do something like > > > <facility id="rhino.esb" > > > > <bus threadCount="1" > > > numberOfRetries="5" > > > endpoint="msmq://localhost/nhprof.web" > > > /> > > > <messages> > > > <add name="nhprof" > > > endpoint="msmq://localhost/nhprof.orders"/> > > > </messages> > > > </facility> > > > > > And then the service app: > > > <facility id="rhino.esb" > > > > <bus threadCount="1" > > > numberOfRetries="5" > > > endpoint="msmq://localhost/nhprof.svc" > > > /> > > > <messages> > > > <add name="nhprof" > > > endpoint="msmq://localhost/nhprof.orders"/> > > > </messages> > > > </facility> > > > On Jan 19, 10:53 am, Ayende Rahien <[email protected]> wrote: > > > > No, there is an assumption that that queue exists. > > > > > > On Mon, Jan 19, 2009 at 11:50 AM, chrisortman <[email protected] > > > > > wrote: > > > > > > > Is there an assumption then that there exists a bus that is > watching > > > > > that endpoint? > > > > > > > On Jan 19, 10:27 am, Ayende Rahien <[email protected]> wrote: > > > > > > inline > > > > > > > > On Mon, Jan 19, 2009 at 10:43 AM, chrisortman < > [email protected] > > > > > > > wrote: > > > > > > > > > Is it correct to say that a Discarded message is any message > that > > > > > > > arrives at an endpoint but has no consumers registered for it? > > > > > > > > yes > > > > > > another option is that this is a saga message that doesn't have a > > > saga > > > > > > instance to orchestrate it. > > > > > > > > > I am also not understanding why messages have their own > endpoint or > > > > > > > when they should share the same endpoint as the bus? > > > > > > > > > I am running the trunk right now, and when I use this as my > config > > > > > > > <facility id="rhino.esb" > > > > > > > > <bus threadCount="1" > > > > > > > numberOfRetries="5" > > > > > > > > > logEndpoint="msmq://localhost/my.log" > > > > > > > endpoint="msmq://localhost/rhino" > > > > > > > /> > > > > > > > <messages> > > > > > > > <add name="MyMessageAssembly" > > > > > > > endpoint="msmq://localhost/my.subscriptions"/> > > > > > > > </messages> > > > > > > > </facility> > > > > > > > > > I get errors because the my.subscriptions queue doesn't exist. > > > > > > > > The problem that you have is that you are trying to send the > message > > > to a > > > > > > non existing bus. > > > > > > > > The reason that you have to specify an endpoint several times is > that > > > the > > > > > > bus' endpoint says what queue the bus listen on. > > > > > > The message endpoint specify what is the owner of a particular > set of > > > > > > messages. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en -~----------~----~----~----~------~----~------~--~---
