REST Web services
REST (representational state transfer) is an approach for getting content from a website by reading a designated webpage that contains an XML (Extensible Markup Language) file that describes and includes the desired content. A basic use case for it would be an online publisher making available syndicated content. Subscribers would need only to know the URL (Uniform Resource Locator) for the page where the XML file was located, read it with a Web browser, interpret the content data, and reformat and use it appropriately. The fundamental difference between REST Web services and document-style Web services is how the service consumer knows what to expect out of the service. Web services have contracts, defined in WSDL. Since Web services focus on the service, rather than on the resource, the consumer has clear visibility into the behavior of the various operations of the service, whereas in RESTful resource-oriented perspective, we have visibility into the resources, but the behavior is implicit, since there is no contract that governs the behavior of each URI-identified resource. Find the latest information about Restful web services in this topic section.
News:1 - 3 of 18
Video: What matters most in micro-services, REST and NoSQL?
23 Oct 2014
News - Jeff Genender discusses REST, NoSQL and how micro-services are changing how people are doing development in this video from JavaOne 2014.
How Java rules improve Android apps: Taming big data with big reasoning
27 Jul 2013
News - Big data technologies are all the rage with enterprise architects and data focused professionals, but with big data isn't a panacea in itself. Big data solutions are only successful when they are accompanied by big reasoning as well.
Dell Boomi and other integration providers jump on API management
10 May 2013
News - After several API management firms were acquired elsewhere, Dell Boomi announces their own API management features, built internally.
Reference & Learning:1 - 3 of 27
Can a pattern become an anti-pattern? How to avoid the loose coupling mistake
15 Jan 2015
Feature - Nobody is debating the benefits of loose-coupling, but far too many SOA architects take the practice too far. Make sure you know when loose-coupling makes sense, and more importantly, when it doesn't.
Creating pages based on a JSF template: Using the Facelets ui:define tag
20 Jul 2014
Tutorial - What do you do once you've set up a handsome page template using the Facelets functions that come with JSF 2.x? Well, you start creating new pages, meshing those ui:define tags in with ui:composition and ui:insert. It's easier than it sounds, trust me.
Conquering the challenge of integrating JAX-RS (REST) with OSGi modularity
06 May 2014
Feature - OSGi and REST based web services are two incredibly popular technologies that have evolved separately over the past few years. But now developers are tackling the challenge of bringing these two technologies together. Here's how they are making that...
Expert Technical Advice:1 - 3 of 8
Getting Java programmers up to speed on Java EE 7 need not be a 'Pilgrimage'
03 Jan 2014
Tip - Here we take a look at the top five features of Java EE 7 that traditional J2EE and standard edition Java developers will want to familiarize themselves. There are some cool features in Java EE 7, but they're evolutionary, not revolutionary, so a little...
Fulfilling nonfunctional requirements with patterns and best practices
07 Jun 2013
Tip - When applications are developed properly using patterns and best practices, nonfunctional requirements tend to be an unintended benefit.
The three imperatives of service oriented software development and design
13 Apr 2013
Tip - When developing service oriented software, SOA architects need to keep in mind these three imperatives in order to develop SOA software effectively.