Comments on: On WSDL http://www.subbu.org/blog/2008/01/on-wsdl Mon, 06 Feb 2012 19:04:25 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Subbu Allamaraju http://www.subbu.org/blog/2008/01/on-wsdl/comment-page-1#comment-203 Subbu Allamaraju Tue, 22 Jan 2008 16:16:11 +0000 http://wp.subbu.org/2008/01/on-wsdl/#comment-203 I agree that there is no alternative. Unfortunately, those that do have success with WSDL are almost always using it by letting a tool translate their programming language interfaces into/out of WSDL. In the absence of an alternative, this is what everyone settled down to. I agree that there is no alternative. Unfortunately, those that do have success with WSDL are almost always using it by letting a tool translate their programming language interfaces into/out of WSDL. In the absence of an alternative, this is what everyone settled down to.

]]> By: Jean-Jacques Dubray http://www.subbu.org/blog/2008/01/on-wsdl/comment-page-1#comment-202 Jean-Jacques Dubray Tue, 22 Jan 2008 10:39:26 +0000 http://wp.subbu.org/2008/01/on-wsdl/#comment-202 Yes, I don't disagree with what you are saying, though again, a) I think there is a need for a major upgrade of the understanding of how to use these technologies. It looks to me that people like Tim or Steve have lost touch with this understanding. I can see it in my everyday life too. b) it s---- in reference to what? what is the alternative to WSDL. Give me a better one and I'll use it. At the end of the day I have a job to do, so I can complain forever about how bad it s---- and use it as an excuse not to do my job, or I can byte the bullet and use it. For me this is the byte code level. I don't know that many people that write at that level often. They probably will say it s----. Another analogy is JavaScript vs GWT. JavaScript s---- badly, cross-browser JavaScript s---- even more. So what do we do? We get rid of it? no. We create GWT. This is what is illarious in this debate, some people are on a mission to kill WS-*, this is all you care, nothing less, nothing more. It does not matter to these poeple what REST can do or cannot do. Well I have news for you that mission is doomed to fail because: a) there are too many projects that use WS-* b) REST has no viable alternative to offer, So where do we go from there? JJ- Yes, I don’t disagree with what you are saying, though again,

a) I think there is a need for a major upgrade of the understanding of how to use these technologies. It looks to me that people like Tim or Steve have lost touch with this understanding. I can see it in my everyday life too.

b) it s—- in reference to what? what is the alternative to WSDL. Give me a better one and I’ll use it.

At the end of the day I have a job to do, so I can complain forever about how bad it s—- and use it as an excuse not to do my job, or I can byte the bullet and use it.

For me this is the byte code level. I don’t know that many people that write at that level often. They probably will say it s—-. Another analogy is JavaScript vs GWT. JavaScript s—- badly, cross-browser JavaScript s—- even more. So what do we do? We get rid of it? no. We create GWT.

This is what is illarious in this debate, some people are on a mission to kill WS-*, this is all you care, nothing less, nothing more. It does not matter to these poeple what REST can do or cannot do. Well I have news for you that mission is doomed to fail because:
a) there are too many projects that use WS-*
b) REST has no viable alternative to offer,

So where do we go from there?

JJ-

]]>