On Aug 5, 2010, at 4:22 PM, Gervas Douglas quotes Brogden: > Jersey Project and the JAX-RS Standard > > [...]
> The Jersey project is attempting to popularize the Web Application > Description Language (WADL) That is actually not true. Yes, there is support for WADL in Jersey, but the people involved more and more understand that WADL is unnecessary (and unRESTful if used at design time). > as a simpler RESTful equivalent to WSDL for describing the resources a > service provides. This XML formatted service description can be generated by > a Jersey service and optionally extended by the developer. It is intended to > make it easy to create client software to access a Jersey service. As far as > I can tell, WADL has not yet been extensively adopted. Right. And let's hope it won't be at all. REST's constraints forbid design time descriptions of services because they lead to coupling between client and server. (Or does your browser need an *DL to interact with Amazon??). Instead of discussing WADL and friends, we should put our educational effort into explaining people that there is no need to describe a service when you are doing REST. All that is necessary to know is which media types are roughly used in the overall system (otherwise you could simply not code a user agent). > The major Web services exposing a RESTful interface, such as Twitter, publish > plain text descriptions of services with examples in various languages. Take not that Twitter is far from exposing a RESTful API. Twitter is an HTTP Type I API (using my own classification): http://nordsc.com/ext/classification_of_http_based_apis.html#http-type-one No description of the Twitter API would be needed if a decent media type would have been defined by them, first. Jan > > Restlet version 2.0 > > The Restlet framework was started as an open source project well before the > JSR-311 committee got organized. When I last looked, the Restlet framework > version 1.1 was the current but version 2 was nearly ready for release. > Version 2.0 (just released in July 2010) accomplished a major revision of the > organization of packages and simplification of the API. This reorganization > makes it possible to use one code base to create five different editions. > Each edition contains support for the basic Restlet classes plus various > extensions as appropriate for each working environment: > > • Java Standard Edition (JSE) > • Java Enterprise Edition (JEE) > • Google App Engine > • Google Web Toolkit (GWT) > • Android > The Restlet developers have been busy increasing the number of extensions to > support industry standards. The version 2.0 Restlet framework supports the > JAX-RS 1.0 API and also the Open Data Protocol (OData) currently being > developed by Microsoft. The Restlet client API emphasizes using the same > interfaces which the server side uses. This approach is in dramatic contrast > with that used by Jersey and other REST clients which tend to emulate the > functions of an HTTP browser client. Restlet documentation gives extensive > examples of development with various IDEs. > > IBM's Project Zero and sMash for WebSphere > > Project Zero has evolved quite rapidly since I last took a look at it. The > incubator project aimed at rapid (Zero complexity, Zero overhead, Zero > obstacles) development has evolved into a product called IBM WebSphere sMash > while the development community continues as Project Zero.Note that Project > Zero is not open source, but provides a way for developers to feed ideas into > the sMash commercial product, while taking advantage of open-source tools > such as Groovy, Dojo and PHP. > > The sMash product, currently at version 1.1, integrates the RESTful style of > Project Zero with other IBM products such as the CICS transaction server. On > the server side, the Java based scripting language Groovy and the popular PHP > scripting language are emphasized. Deployment of services can be on WebSphere > servers, Amazon's EC2 Cloud, or the IBM System z based private cloud. On the > browser side sMash uses the popular Dojo JavaScript library. > > Resources > > Release notes for Restlet 2.0 > > My article on REST versus SOAP > > This Wikipedia article lists additional frameworks in a variety of languages > > Specification of WADL as submitted to the W3C > > REST Tutorial on SearchSOA.com>> > > You can find this at: > http://searchsoa.techtarget.com/tip/0,289483,sid26_gci1517841,00.html?track=NL-449&ad=777121&asrc=EM_NLT_12174656 > Gervas > > > > ----------------------------------- Jan Algermissen, Consultant NORD Software Consulting Mail: [email protected] Blog: http://www.nordsc.com/blog/ Work: http://www.nordsc.com/ ----------------------------------- ------------------------------------ Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/service-orientated-architecture/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/service-orientated-architecture/join (Yahoo! ID required) <*> To change settings via email: [email protected] [email protected] <*> 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/
