On Apr 1, 2006, at 12:41 PM, Steve Ross-Talbot wrote: > If you were building an application that is totally within an > enterprise what compelling reason would make you even look at WS-RM? I > can see if you cross organisational boundaries this stuff might be > attractive but if you are within a domain of control (an organisation) > then I cannot see why you would use WS-RM. If you have MSoft on the > desk top you can always use ASP.NET Web Service style and pass to a > service that is a proxy for JMS. Any light on this would be most > welcome. > > I might just be behind the times. >
WS-RM is a (or will be) an interoperability standard, JMS is an API. Relying on JMS makes your applications portable, relying on WS-RM will someday make them interoperable. To me, standardizing on protocols, not programming APIs, is a key feature of SOA. Stefan -- Stefan Tilkov, [EMAIL PROTECTED], http://www.innoq.com/blog/st/ Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/service-orientated-architecture/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
