[jbossws-dev] [Design of JBoss Web Services] - Re: ws-eventing: event notification failure

[heiko.braun@jboss.com]

sorry stefano, i missed this one. here are my two cents:

a) notification failures: sure, it sound reasonable to track them through the SubscriptionManager. Resending (means queuing) would require additonal constraints (expiration policy, softening, etc). This already sounds like jms integration to me. I was thinking about that in the beginning, if further QoS capabilities can be delegated to an JMS instance.

b) clustered environment: this would needs to be elaborated further. Could you provide some diagrams? We could use the WIKI for this...

c) Did you take alook at WS-Notifcation? WS-Eventing is kept really simple, WSN adds a lot of concepts. It might be worth comparing these specs before actually modifiying the WS-Eventing codebase.

d) If you have fun coding these issues, i have fun helping you out where ever i can. Please contact me directly if you need any additional svn privileges. 

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3984464#3984464

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3984464