Comments on: POX Interpretation of REST http://www.subbu.org/blog/2008/07/pox-interpretation-of-rest Wed, 08 Feb 2012 05:16:45 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: On REST WSDL 2.0 Demo at subbu.org http://www.subbu.org/blog/2008/07/pox-interpretation-of-rest/comment-page-1#comment-3990 On REST WSDL 2.0 Demo at subbu.org Sun, 28 Sep 2008 10:46:15 +0000 http://wp.subbu.org/2008/07/pox-interpretation-of-rest/#comment-3990 [...] response to some recent comments by me, and perhaps several others, Keith Chapman has put together a demo to illustrate that WSDL [...] [...] response to some recent comments by me, and perhaps several others, Keith Chapman has put together a demo to illustrate that WSDL [...]

]]> By: Keith Chapman http://www.subbu.org/blog/2008/07/pox-interpretation-of-rest/comment-page-1#comment-2827 Keith Chapman Mon, 15 Sep 2008 18:55:59 +0000 http://wp.subbu.org/2008/07/pox-interpretation-of-rest/#comment-2827 Subbu / Mike, I've put up a <a href="http://www.keith-chapman.org/2008/09/restfull-mashup-with-wsdl-20-wso2.html" rel="nofollow">blog POST that shows how WSDL 2.0 cab be used to describe a RESTfull Service.</a>. This service is publicly available and you can try it out your selves. The service can be accessed using WS-* as well as REST. Wuld like to know your thoughts on this. Subbu / Mike,

I’ve put up a blog POST that shows how WSDL 2.0 cab be used to describe a RESTfull Service.. This service is publicly available and you can try it out your selves. The service can be accessed using WS-* as well as REST. Wuld like to know your thoughts on this.

]]> By: Mike Amundsen http://www.subbu.org/blog/2008/07/pox-interpretation-of-rest/comment-page-1#comment-309 Mike Amundsen Wed, 06 Aug 2008 19:24:48 +0000 http://wp.subbu.org/2008/07/pox-interpretation-of-rest/#comment-309 Sanjiva: my primary issue w/ REST/POX hybrids is that they are usually only a 'shallow' copy of what REST really means. REST is not uniform interface (only). REST is not URL construction (only). REST also focuses on the importance of metadata (as HTTP Headers); the role of intermediaries (caching/authentication proxies); handling code-on-demand properly; and other base-line issues. i don't see this level of REST support in JSR-311 or others that try to support both (MSFT's WCF comes to mind). Sanjiva:

my primary issue w/ REST/POX hybrids is that they are usually only a ‘shallow’ copy of what REST really means. REST is not uniform interface (only). REST is not URL construction (only). REST also focuses on the importance of metadata (as HTTP Headers); the role of intermediaries (caching/authentication proxies); handling code-on-demand properly; and other base-line issues.

i don’t see this level of REST support in JSR-311 or others that try to support both (MSFT’s WCF comes to mind).

]]> By: Sanjiva Weerawarana http://www.subbu.org/blog/2008/07/pox-interpretation-of-rest/comment-page-1#comment-301 Sanjiva Weerawarana Sat, 26 Jul 2008 11:18:22 +0000 http://wp.subbu.org/2008/07/pox-interpretation-of-rest/#comment-301 Subbu, let me give you an example. REST community considers JSR-311 annotations RESTful right? OK, so suppose I take a simple Java class and put both JSR-311 annotations and JAX-WS annotations to make that class into a WS-* service too. Effectively that class is offering (presumably) a "good" RESTful service and a WS-* one. I actually do not think this is the right way to write services at all (taking any old class and flipping switches) but I'm not sure the tools we have for handling XML, MIME etc., especially in Java, really encourage developers to get their hands dirty yet. Subbu, let me give you an example. REST community considers JSR-311 annotations RESTful right? OK, so suppose I take a simple Java class and put both JSR-311 annotations and JAX-WS annotations to make that class into a WS-* service too.

Effectively that class is offering (presumably) a “good” RESTful service and a WS-* one.

I actually do not think this is the right way to write services at all (taking any old class and flipping switches) but I’m not sure the tools we have for handling XML, MIME etc., especially in Java, really encourage developers to get their hands dirty yet.

]]> By: Subbu Allamaraju http://www.subbu.org/blog/2008/07/pox-interpretation-of-rest/comment-page-1#comment-300 Subbu Allamaraju Fri, 25 Jul 2008 18:46:58 +0000 http://wp.subbu.org/2008/07/pox-interpretation-of-rest/#comment-300 Nice. Look forward to reading it. Nice. Look forward to reading it.

]]> By: Keith Chapman http://www.subbu.org/blog/2008/07/pox-interpretation-of-rest/comment-page-1#comment-299 Keith Chapman Fri, 25 Jul 2008 08:36:11 +0000 http://wp.subbu.org/2008/07/pox-interpretation-of-rest/#comment-299 Well Axis2 does support REST as well as POX. And so does WSO2 WSAS, WSO2 Mashup Server, WSO2 WSF/{C,C++,PHP,Perl} etc... And when I say axis2 supports REST I really mean it. I will explain this in detail in a article. Well Axis2 does support REST as well as POX. And so does WSO2 WSAS, WSO2 Mashup Server, WSO2 WSF/{C,C++,PHP,Perl} etc… And when I say axis2 supports REST I really mean it. I will explain this in detail in a article.

]]> By: Mike Amundsen http://www.subbu.org/blog/2008/07/pox-interpretation-of-rest/comment-page-1#comment-298 Mike Amundsen Thu, 24 Jul 2008 22:15:16 +0000 http://wp.subbu.org/2008/07/pox-interpretation-of-rest/#comment-298 i started asking the same question recently. i am an early tester for MSFT's SQL Server Data Services (SSDS) - their cloud db offering. Their current plan is to support both REST and SOAP. it's early, and some things are a bit muddled, but i will say that, so far they seem to be making strides at being REST-ful. but problems will arise. there will be some compromises. it should prove interesting. i started asking the same question recently. i am an early tester for MSFT’s SQL Server Data Services (SSDS) – their cloud db offering. Their current plan is to support both REST and SOAP. it’s early, and some things are a bit muddled, but i will say that, so far they seem to be making strides at being REST-ful.

but problems will arise. there will be some compromises. it should prove interesting.

]]>