Showing messages 1 through 9 of 9.

• who cares
  2007-02-20 23:51:10 parmenion0 [Reply | View]
  
  another storm in a teacup in webmonkey land

• Java is becoming a whore
  2007-02-20 15:46:45 ewin [Reply | View]
  
  Java is trying to please every one - a little bit. Instead of focusing on Java's strength (if you can find one), Java these days tries to be everything for everyone. Only that yet another bug-ridden half-arsed designed-by-committee buzzword-compliant API or language extension will not make Java any better.

  People have apparently not learned from the generics disaster. I have the feeling that running a JSR has much more to to with prestige and vanity than with improving Java.

• it won't be simpler
  2007-02-20 08:12:56 agoubard [Reply | View]
  
  REST won't be simpler for the following reasons:
  * REST is used to access/manage resources. What is the resource for "int multiply(int a, int b)"?
  * You resources are accessed/managed through the different HTTP methods. So except for HTTP GET, you will have difficulties to use put,post,delete.
  * There isn't any good specification of REST, you have the document of Roy Fielding and Wikipedia
  * I haven't seen any REST Web Services so far, all I see are resources accessible using HTTP GET
  * I'm not the only one having this opinion as I talked recently with another person implementing REST for his Web Services framework (like I do) and we shared the same opinion.
  * I don't even mention the caching feature described in Wikipedia.
  
  The simpler way is to have Web Services accessible using HTTP GET or POST as done in Axis 2 or XINS.
• it won't be simpler
  2007-02-21 11:21:37 damnhandy [Reply | View]
  
  What is the resource for "int multiply(int a, int b)"?

  It could be:

  http://localhost/calculations/multiply?a=4&b=4

  But this is silly argument against REST because you're dealing with coarse-grained objects. This woudl be a dumb idea even for WS style web services

  I haven't seen any REST Web Services so far, all I see are resources accessible using HTTP GET

  Have a look at the Flickr API then. Also Yahoo! News

  I'm not the only one having this opinion as I talked recently with another person implementing REST for his Web Services framework (like I do) and we shared the same opinion.

  Awesome.

  One thing most folks fail to see if that browsers don't supprt WSDL or SOAP. A browser can use a RESTful Web Service as part of an AJAX-based web application. Can't quite do that with SOAP and have it work everywhere.

• it won't be simpler
  2007-02-22 02:11:20 agoubard [Reply | View]
  
  Have a look at the Flickr API then. Also Yahoo! News
  
  Well, I've looked at it and it's not REST. it's POX (Plain Old XML).
  From the Flickr REST page: "REST is the simplest request format to use - it's a simple HTTP GET or POST action.". So you see they admit it themself.
  
  As for
  From the Yahoo News! page: "Most API requests will use GET. If the specific documentation requires POST, see the section on POST URL construction below.". Once again not REST, just POX.
  
  One thing most folks fail to see if that browsers don't supprt WSDL or SOAP. A browser can use a RESTful Web Service as part of an AJAX-based web application. Can't quite do that with SOAP and have it work everywhere.
  
  Indeed supporting SOAP for Web Browser is possible but complicated. REST would be a easier than SOAP. POX would be easier than REST. And JSON or JSON-RPC would be easier than POX for AJAX.

• JAX-WS
  2007-02-18 14:38:14 rickcarson [Reply | View]
  
  JAX-WS Webservices kick so much butt, why would you bother with anything else?

  REST might have made sense in the bad, evil and wrong old days of JAX-RPC and WSDL twiddling, but now that we have a superior technology, why go back to reinvent the wheel?

  I suppose that this is the kind of thing that the guys who went and retrofitted RMI to use Corba, even though Corba was the inferior technology, would think of.

  JAX-WS FTW!

• JAX-WS
  2007-02-19 02:17:06 alexter [Reply | View]
  
  CORBA vs. RMI and REST vs. JAX-WS is wrong analogy. First, REST is not a technology like CORBA – it’s an architectural style chosen for reasons unrelated to “superior and inferior”. Second, REST is the _simpler_ alternative here; sometimes you just don’t need anything else. So I would say why would you bother with JAX-WS if all you need is REST.
  
  P.S. I guess REST advocates will have stronger arguments and stronger words :)
• JAX-WS
  2007-02-21 14:41:04 rickcarson [Reply | View]
  
  > Second, REST is the _simpler_ alternative here;
  
  I see you your claim of simpler, and I raise you one @WebService

• approve
  2007-02-16 07:14:26 alexter [Reply | View]
  
  Nice thing to have, even though what Marc Hadley has shown on his blog looks more like simply annotation-based server HTTP API. In my mind a web service is something more high-level (though maybe I’m missing something). But this way it’s even better.