Whenever you start thinking stuff is stable, it turns out that it is not the case. I am trying to implement a WS-Eventing compliant service and of course I ran into the issue that that specification sits on the August 2004 edition (and W3C submission) of WS-Addressing while WSE 2.0 sits on the March 2004 edition of WS-Addressing. To implement WS-Eventing correctly, I would now have to write a WS-Adressing implementation parallel to the one existing in WSE 2.0, because - of course - the August 2004 edition sports a new namespace and has a subtly different schema. Unfortunately, the March 2004 edition of WS-Addressing  is so fundamental for WSE 2.0 that routing and security and everything would sit on the March version while my own eventing functionality and nothing else would ride on the August version at the same time and in the same message. Of course that seems just totally wrong.  WSE 2.1, please!

Friday, October 22, 2004 9:47:28 PM UTC
Welcome to the club... :)
Friday, October 22, 2004 10:08:40 PM UTC
This is the *exact* problem I hit earlier this month while implementing WS-Eventing vLatest. Nevertheless, let me know if/when you get your bits up & running. We can conduct an interop session with the Plumbwork Orange bits:

http://sourceforge.net/projects/plumbworkorange/
Friday, October 22, 2004 10:30:52 PM UTC
been through that pain too
Saturday, October 23, 2004 12:00:16 AM UTC
This overall problem (WS-* specs changing) has been a regular problem for my company. I don't know that WSE 2.1 will help all that much in the long run...

http://ewal.net/PermaLink,guid,c0c80ce6-c2cb-48fa-a252-1646c76bb830.aspx
Monday, October 25, 2004 3:52:41 PM UTC
I totally agree. But it's a more general problem, tied to many WS-* specifications.
Comments are closed.