I have a bare-bones document store that consists of a client assembly and a windows service that communicate with each other using Rhino- esb. The client assembly is not an application in and of itself but just provides an API for applications to use when interacting with the store. The API supports two basic types of operations. It can send basic CRUD messages to the store and/or it can subscribe to notifications from the store that the store publishes (DocAdded, DocDeleted, etc.) Thus a scan app can use the client to put docs into the store and an OCR app might listens for notifications about new documents so that they can be OCRed.
The problem I am having, using the scenario above as an example, is that when the scan app submits a new document, it also receives back the DocAdded message even though it has not subscribed to it. The client API has a handler for the message (because it has handlers for all potential notification messages) but , in this case, because the client API did not subscribe to any messages, those handlers are not configured (i.e the scan app has not told the API what to do if it received such a message because the scan app does not care about such events). As a result the handler is throwing an error, as is should. Am I missing something in how Rhino-esb works? I know that if, while handling a message, I send a REPLY, it goes back to the original sender. But in handling a message, if I PUBLISH a message, does that to go back to the original sender as well, even if it is not subscribed? I can work around this by coding the handlers to simply ignore messages for which it is not configured, but I would prefer not to do this because that would mask certain configuration errors that would present in this same manner. Regards, Ken -- 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.
