You can subclass SimpleSubscriptionManager, override that method to do what you want, and then just change the name of the class used for the subscription capability in muse.xml. Like this:
<capability> <capability-uri>http://docs.oasis-open.org/wsn/bw-2/SubscriptionManager</capability-uri> <java-capability-class>your.new.subclass.MySubcriptionManager</java-capability-class> </capability> And you are correct - it does not re-try missed notifications. Dan [EMAIL PROTECTED] wrote on 10/25/2006 05:24:49 AM: > Hi Daniel, > > Thanks for your answer. I'm afraid that what I need is not only to see > the error in the log message but also be able to deal with it and > communicate to other parts of my system that the sending of the message > X to the suscriptor Y has failed. > To do that, I think that the best option for me is to modify the method > publish in the > org.apache.muse.ws.notification.imple.SimpleSubscriptionManager class, > isn't it? > > By the way, just to ensure my thoughts... If the sending of a > notification fails, will the subscription manager try to send it again > after period of time? I guess the answer for that is NO, but could you > please confirm it? > > Thanks in advance, > > David > > Daniel Jemiolo escribió: > > >Hi David, > > > >If you turn the SOAP tracing on for subscriptions, you can see the SOAP > >message that went out just prior to the exception. The wsa:To SOAP header > >will have the address of the consumer that is not responding. The info on > >this setting is at the bottom of this page: > > > > http://ws.apache.org/muse/docs/2.0.0/manual/capabilities/wsn-sub.html > > > >That said, a custom message would be better than the terse java.net > >message. If you open a JIRA item for it, I will add some subscription data > >to the log message so you don't have to compare against the SOAP. > > > >Dan > > > > > > > >[EMAIL PROTECTED] wrote on 10/23/2006 10:47:19 AM: > > > > > > > >>Hi everyone, > >> > >>I was using pubscribe1.1. and now I've started to try muse-2.0. For both > >> > >> > > > > > > > >>distributions I got the same question: when a consumer goes down I can > >>read in the producer log the next exception (muse-2.0 log): > >> > >>INFO: There was an error while processing a request: > >> > >>Connection refused > >> > >> > >> > >> > >> > >org.apache.muse.core.AbstractResourceClient.invoke(AbstractResourceClient.java:254) > > > > > >>org.apache.muse.ws.notification.remote.NotificationConsumerClient. > >>notify(NotificationConsumerClient.java:95) > >> > >>org.apache.muse.ws.notification.impl.SimpleSubscriptionManager. > >>publish(SimpleSubscriptionManager.java:204) > >> > >>org.apache.muse.ws.notification.impl.SimpleNotificationProducer. > >>publish(SimpleNotificationProducer.java:435) > >> org.apache.ws.muse.test.wsrf.MyCapability$1.run(Unknown Source) > >> > >> > >>If there are some consumers subscribed to the same topic, is it possible > >> > >> > > > > > > > >>to know in the producer side which consumer is exactly causing the > >>error? How can I do it? > >>Thanks, > >> > >>David > >> > >> > >>--------------------------------------------------------------------- > >>To unsubscribe, e-mail: [EMAIL PROTECTED] > >>For additional commands, e-mail: [EMAIL PROTECTED] > >> > >> > >> > > > > > >--------------------------------------------------------------------- > >To unsubscribe, e-mail: [EMAIL PROTECTED] > >For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
