--- In [email protected], Gregg Wonderly <[EMAIL PROTECTED]> wrote: > kawaijenbromo wrote: > > *Cons:* > > > > * Probably the implementations are not very stable (sort of 1.0 > > releases) > > * It is not a real standard due to the standard battle with > > WS-eventing which will not converge before years
> > Can you elaborate on what you think is the biggest reason why there is not > convergence and/or few faithful, debugged implementations? I have my own > thoughts that revolve around the details of all these pieces. But, I'm curious > what you've experienced, seen and heard. > > Gregg Wonderly IMHO, this specific one is entirely political. WS-* is in bad shape for various reasons; some are technical because there are intrinsic technical hard problems (such as WS-RM with the interoperable persistence issues), some are religious with RESTful versus SOAP. But for what regards WS-EventingNotification which is the latest ugly avatar of the eventing mess, I can see no other reason than the fact that MS and IBM have evaluated that converging on SOAP/WSDL is enough, and the rest must remain proprietary. Not stupid if you look at the WebSphere *integration* and Biztalk businesses. I see no tehchnicalities which should hamper convergence. But I would like to hear other opinions ! So the primary victims are us, the users, because a universal PubSub would be a powerful enabler to complement SOA with some EDA. It is already rather difficult to convince SW architects to think in EDA terms for some use cases; but with the lack of a clear technology, it becomes a real uphill battle. jacques talbot
