James, We are making good progress for both WS-Eventing and WS-Notification in our hermes project. Can we get u guys interested?
thanks, dims On Fri, 8 Oct 2004 09:00:49 +0100, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > On 7 Oct 2004, at 18:08, Davanum Srinivas wrote: > > James, > > > > Can you please help us understand your needs wrt to WS-Eventing in > > ActiveMQ project. We are planning to start a project for WS-Eventing > > and possibly WS-Notification and wanted to know about your xmlbeans > > based code > > (http://cvs.activemq.codehaus.org/viewrep/activemq/modules/ws- > > eventing) > > and whether you are using Axis etc... > > We've implemented a full message broker capable of implementing high > performance, publish/subscribe and queue based messaging with durable > and transient subscriptions, transactions, clustering, discovery, load > balancing, flow-control, message timeout, filters & reconnection etc. > > So we figured, we might as well reuse ActiveMQ to be a WS-Eventing > implementation, particularly as WS-Eventing maps pretty trivially to > most of what we've already implemented in ActiveMQ. Indeed from the > message broker perspective, WS-Eventing is just a different WireFormat > to create & keep alive subscriptions and deliver them - so it should be > pretty easy and quick to implement. > > From an implementation perspective we've not got very far though - so > far all we've done is create the XMLBeans for the WS-Eventing spec :). > If you wanted to create a WS-Eventing implementation please do go for > it. Maybe an implementation which delegated to the JMS API might be a > useful start, then we could drop ActiveMQ in as an implementation? > > Let us know how you get on as its good to avoid duplicating work. > > James > ------- > http://radio.weblogs.com/0112098/ > > -- Davanum Srinivas - http://webservices.apache.org/~dims/
