Showing posts with label rest. Show all posts
Showing posts with label rest. Show all posts

Tuesday, October 19, 2010

DevReach 18+19 October Sofia, Bulgaria (part5)

...continued

Designing Applications in the era of Many-core Computing:

This session was about making a unparalleled program use all cores of a CPU.
The presenter was a Romanian so his program was the recipee for making goulash.
He used threading on a higher level with a structure called a Task.
A tasks can be combined to be one after another by a lambda expressions.


Building RESTful Applications with the Open Data Protocol

The last session I attended was one regarding RESTful services.
The presenter was very high-spirited and it was a joy to listen to his explanations.
So REST services is exposing a service to be accessed  via pure URL address through the browser. 
Using the HTTP methods POST GET UPDATE DELETE to access the service if you have the access rights.

He demonstrated how to connect to such a service via a client.

He created an REST service. 
He showed an easy API to do paging for the service.

It was a very nice presentation. 

L.K. 

Thursday, October 07, 2010

Java2Days Sofia Day 1 (part5)

Quotes from other sessions not that interesting:

JSF has no pros
Oracle + Sun =  Snoracle

16:00 - 5. Building RESTFul Web Services with Java  Vassil Popovski, VMware

REST Principles:
-- everything is a resource
-- resources have identifiers
-- uniform access
-- resources have representations
-- link things together

HTTP methods
POST UPDATE GET DELETE

JAX-RS - java API for rest services. The presenter says that this SRS seems readable.

java.ws.rs.*

JAX-RS = POJO + Annotations

Best implementation of JAX-RS is CXF

Key concepts
- resource classes - have at least 1 resource method
- resource methods - annotated with @POST @GET etc
- provider classes  - extending JAX-RS interface

More commonly-used annotations:
@Path - relative path for a resources
@Consumers / @Produces - for media types
 - produces = output
 - consumes = input
@PathParam
@Context
@QueryParam - inject the value of a query into a variable

Benefits:
- scalable solutions
- compared to SOAP is much simpler

(next-page)