Re: WS-Addressing Implementation

[Davanum Srinivas]

We all have our pet peeve's and skeletons we'd like to bury :)

Do you want to work on WS-Resource* on ws-fx as well? I was thinking of taking a stab 
at either
WS-Eventing or WS-Notification soon.

thanks,
dims

--- Steve Loughran [EMAIL PROTECTED] wrote:
 Ias wrote:
 FYI, http://ws.apache.org/ws-fx/addressing/
  
  Thanks very much for your nice work!
  
  Hoping Apache Addressing's thriving future with interest and participation
  from people everywhere,
  
 
 While I am glad that we are keeping up with the WS-* standards, I am 
 unsure about the whole sub-addressing feature of WS addressing (or 
 alternate proposals), that essentially add a new destination to a 
 endpoint above and beyond the current (url,SOAPAction) tuple. Now every 
 header can take a ws-addressing address and use that to redirect the 
 message.
 
 That may let you tack on more stuff to the same endpoint, but at the 
 same time the nice and simple notion of one url, one service is lost. 
 It almost represents the complete divorce of WS-* from the REST 
 architecture.
 
 Thank you for the code though Dims! I will be using it in 
 WS-ResourceFramework related stuff :)
 


=
Davanum Srinivas - http://webservices.apache.org/~dims/

RE: WS-Addressing Implementation

[David A. Chappell]

 -Original Message-
 From: Steve Loughran [mailto:[EMAIL PROTECTED] 
 Sent: Thursday, February 12, 2004 9:07 AM
 To: [EMAIL PROTECTED]
 Subject: Re: WS-Addressing Implementation
...
 Actually, if you are going to do any of them, ws-eventing is 
 a lot, lot simpler. ws-notification scares me.

Awe c'mon, its not that bad.  Its pub/sub for Web services.  How cool is
that?  It really ought to be broken up into smaller specs, and made
composable with WS-Eventing.  But other than that, its heart is in the
right place.
Dave