Download as PDF, PPTX
![Method Parameters
• Session
• Implicitly supported types
– String, byte[]
– JsonArray, JsonObject
• More types supported by Encoders](https://image.slidesharecdn.com/web-technologies-in-java-ee-131211082145-phpapp02/85/Web-Technologies-in-Java-EE-7-50-320.jpg)
![Method Parameters
• Session
• Implicitly supported types
– String, byte[]
– JsonArray, JsonObject
• More types supported by Encoders](https://image.slidesharecdn.com/web-technologies-in-java-ee-131211082145-phpapp02/75/Web-Technologies-in-Java-EE-7-50-2048.jpg)
Uploaded byLukáš Fryč
Web Technologies in Java EE 7
This document discusses various web technologies in Java EE including JSF 2.2, JAX-RS 2.0, JSON-P, and WebSocket. It provides an overview of client-side vs server-side web approaches, describes the capabilities and goals of each technology, and demonstrates examples of using JAX-RS for RESTful services, the JSON processing APIs, and WebSocket. The document is presented by Lukas Fryc, a software engineer at Red Hat interested in Java EE, HTML5, and Web Components.
More Related Content
![Java Web Services [2/5]: Introduction to SOAP](https://cdn.slidesharecdn.com/ss_thumbnails/jws-chapter2-130106065304-phpapp01-thumbnail.jpg?width=600ounds&width=560&fit=bounds)
![Java Web Services [5/5]: REST and JAX-RS](https://cdn.slidesharecdn.com/ss_thumbnails/jws-chapter5-130106065549-phpapp01-thumbnail.jpg?width=600ounds&width=560&fit=bounds)
![Java Web Services [3/5]: WSDL, WADL and UDDI](https://cdn.slidesharecdn.com/ss_thumbnails/jws-chapter3-130106065523-phpapp01-thumbnail.jpg?width=600ounds&width=560&fit=bounds)
![Java Web Services [1/5]: Introduction to Web Services](https://cdn.slidesharecdn.com/ss_thumbnails/jws-chapter1-130106065040-phpapp02-thumbnail.jpg?width=600ounds&width=560&fit=bounds)
![Java Web Services [4/5]: Java API for XML Web Services](https://cdn.slidesharecdn.com/ss_thumbnails/jws-chapter4-130106065907-phpapp02-thumbnail.jpg?width=600ounds&width=560&fit=bounds)
Similar to Web Technologies in Java EE 7
Web Technologies in Java EE 7
- 1. Web Technologies in JavaEE JSF 2.2, JAX-RS 2.0, JSON-P, WebSocket
- 2. Agenda • • • • • Client-Side vs Server-SideWeb JAX-RS 2.0 RESTful Services JSON-P Java API for JSON Processing Java API for WebSocket JSF 2.2 Java Server Faces
- 3. $ whoami • LukášFryč – Software Engineer, JBoss, Red Hat • RichFaces & Arquillian Core Developer – Interests • • • • Living and advocating Java EE (6 yrs) HTML5, Web Components, AngularJS Running, Hiking Spending time with my family
- 4.
- 5. Client- vs. Server-SideWeb • Server-Side Web (Thin Client) – Well-established approach – 90's, 00's • Client-Side Web (Thick Client) – Modern approach – Fully leverages enhancements in web standards and protocols – 10's
- 6.
- 7.
- 8. Client-Side Web Approach •Off-loading server – Scalability, Stateless • Client-Side Frameworks – AngularJS, Ember, Backbone, Errai, Polymer, .......... • Standards improvements – HTML5 + Protocols • REST interfaces – Data-oriented, presentation independent
- 9. Java API forRESTful Services JAX-RS 2.0
- 10. JAX-RS Origins • RESTfulPrinciples – Assign everything an ID – Link things together – Use common methods (GET, POST, ...) – Stateless communication
- 11. JAX-RS 1.0 Goals •POJO-Based API • HTTP Centric • Format Independence – plain/text – XML – HTML – JSON
- 12. JAX-RS API • Resources –@Path • HTTP methods – @GET / @POST / @PUT / @DELETE / ... • Parameters – @PathParam / @QueryParam / ... • Media-Type – @Consumes / @Produces
- 13.
- 14. HTTP Method Purpose Method Meaning @GET Read,possibly cached @POST Use to modify or update a resource or create new one (without known ID) @PUT Create a resource or overwrite existing ( with known ID) @DELETE Remove @HEAD GET with no response @OPTIONS Supported methods
- 15. Parameter Injection Annotation Example @PathParam(“id”) @Path(“/consumer/{id}”) @QueryParam(“query”) GET /consumer/search? query=??? @CookieParam(“userna me”) Cookie:... @HeaderParam(“Authori zation”) Header: Authorization: ... @FormParam(“inputNa me”) @Consumes("multipart/form-data") @MatrixParam GET /consumer/search;query=???
- 16. New in JAX-RS2.0 • New Features – Client API – Filters and Interceptors – Asynchronous API – Hypermedia • Improvements – Content-Type Negotiation – Validation Alignments
- 17. Client API • HTTPclient libraries too low-level • Need for standardization
- 18.
- 19. Filters and Interceptors •Customize JAX-RS – via well-defined extension points • Use cases: – Logging – Compression – Security • Shared between server & client
- 20. Filters • Non-wrapping extensionpoints – Pre: RequestFilter – Post: ResponseFilter • Part of a filter chain • Do not call the next filter directly • Each filter decides to proceed or break chain – FilterAction.NEXT, FilterAction.STOP
- 21. Interceptors • Wrapping extensionspoints – ReadFrom: ReaderInterceptor – WriteTo: WriterInterceptor • Part of an interceptor chain • Call the next handler directly • Each handler decides to proceed or break chain – By calling ctx.proceed();
- 22. Asynchronous • Let “borrowed”threads run free! – Suspend and resume connections • Suspend while waiting for an event (@Suspended AsyncResponse) • Resume when event arrives • Leverages Servlet 3.x async support – HttpServletRequest.upgrade(ProtocolHandler) • Client API support – Future<T>, InvocationCallback<T>
- 23.
- 24. Validation • Constraint annotations –Fields and properties – Parameters • Including request entity – Methods • Response entities – Resource classes • Custom constraints
- 25. Demo JAX-RS – BeanValidation
- 26. Hypermedia • Link types –Structural links • <customer>http://.../customers/1234</customer> – Transitional links • Links: <http://.../cancel>; rel=cancel
- 27. Java API forJSON Processing JSON-P
- 28. Motivation: JSON • JavaScriptObject Notation – The format of the Web • Comes from JavaScript object syntax • Human-Readable – Language independent • Standard parsers in many languages – Key-value Pair Format { “firstName”: “John”, “lastName”: “Smith” }
- 29. Motivation: Java APIfor JSON • Lot of vendor-dependent APIs – Need for standardization • Standard API for JSON processing – parse, generate, transform • Binding? Querying?
- 30. JSON-P APIs • StreamingAPI • Similar to XML DOM • Object Model API • Similar to StAX
- 31. JSON-P APIs • StreamingAPI – JsonParser, JsonGenerator • Object Model API – JsonObject, JsonArray – JsonBuilder – JsonReader, JsonWriter
- 32. Object Model -JsonReader • Reads JsonObject and JsonArray – I/O Reader, InputStream • Uses pluggable JsonParser // Reads a JSON Object try (JsonWriter reader = Json.createReader(io)) { JsonObject obj = reader.readObject(); }
- 33. Object Model -JsonWriter • Writes JsonObject and JsonArray to output source – I/O Writer, OutputStream • Uses pluggable JsonGenerator • Allows pretty-printing and other features // Writes a JSON Object JsonObject obj; try (JsonWriter writer = Json.createWriter(io)) { Writer.writeObject(obj); }
- 34. Object Model –Json*Builder • Chained API – For bulding JsonObject and JsonArray • Can consume JsonObject and JsonArray – Type-safe (no mixing arrays/objects) • Json.createObjectBuilder() • Json.createArrayBuilder()
- 35.
- 36. Streaming - JsonParser •Parses JSON in a streaming way from input sources – Similar to StAX’s XMLStreamReader – a pull parser • Json.createParser()
- 37. Streaming - JsonGenerator •Generates JSON in a streaming way to output sources – Similar to StAX’s XMLStreamWriter • Json.createGenerator()
- 38.
- 39. Java API forWebSocket
- 40. Motivation • HTTP ishalf-duplex • HTTP is inefficient • HTTP hacked to achieve Push – HTTP Polling – HTTP Long-Polling (Comet) – Server Sent Events
- 41. HTTP Upgrade -Request GET /socket/updates HTTP/1.1 Upgrade: WebSocket Connection: Upgrade Host: www.sample.org
- 42. HTTP Upgrade -Response HTTP/1.1 101 WebSocket Protocol Handshake Upgrade: WebSocket Connection: Upgrade
- 43. WebSocket • Full duplex& efficient communication • A component of HTML5 – JavaScript API under W3C – Protocol under IETF • Wide support for browsers – http://caniuse.com/#feat=websockets
- 44. WebSocket: Limitations • Useof existing infrastructure – Proxies doesn't have to handle connection upgrade • Fallback mechanisms – Atmosphere
- 45. WebSocket: Trade-offs • WebSocket –Low efforts to maintain TCP connection – Limited by number of available sockets on one machine – Highly interactive applications • I.e. don't use if you don't expect high amount of transfered messages • HTTP – Resource-consuming protocol – Fairly interactive applications
- 46. WebSocket: Use Cases •Realtime, truly low latency – Chat applications – Live sports ticker – Realtime updating social streams – Multiplayer online games • Requires architecture shift to – Non-blocking IO – Event queues
- 47. Java API forWebSocket • Programmatic • Annotation-based – our focus
- 48. WebSocket Annotations • @ServerEndpoint –@OnOpen – @OnMessage – @OnClose
- 49.
- 50. Method Parameters • Session •Implicitly supported types – String, byte[] – JsonArray, JsonObject • More types supported by Encoders
- 51. Integration to JavaEE 7 • Relation to Servlet 3.1 – HttpServletRequest.upgrade(ProtocolHandler) • Dependency Injection – CDI beans – EJB beans • Security – ws://... vs. wss://... – web.xml: <security-constraint>
- 52.
- 53. JSF Origins • MVCFramework – Component-oriented – Server-Side – Extensible • Component Libraries
- 54. Component Libraries • Richcomponents – RichFaces – PrimeFaces – ICEFaces • Functionality – PrettyFaces – OmniFaces
- 61. JSF 1.0 Goals •What it adds over other frameworks? – Maintainability – Tooling Support – I18N
- 62. JSF 1.0 Goals •What it adds over other frameworks? – Maintainability – Tooling Support – I18N
- 63. JSF 1.0 • • • • • • • Components Renderers Managed beans(CDI) Converters / Validators Navigation Request lifecycle Error handling
- 64. JSF 2.0 • • • • • • • Facelets (asdefault VDL) Composite Components AJAX Resource Libraries Behaviors GET support - <f:viewParam> Project Stage
- 65. JSF 2.2 • BigTickets – Performance, Markup, Multi-tenancy • Small Features – <f:viewAction> – CSRF protection – ClientWindow – Favours CDI • Many smaller improvements
- 66. JSF 2.2 • StatelessViews • (Performance) • HTML5 Friendly Markup • (Modern Markups) • Flows, Resource Library Contracts • (Multi-Tenancy)
- 67. Stateless JSF • Whatis state? – UI Components, Model, Persistence – Developer's concern • Implementation – <f:view transient=”true”>
- 68. HTML5 Friendly Markup JSFComponents <html> <my:colorPicker value=“#{colorBean.color2}” /> <my:calendar value=“#{calendarBean.date1}” /> </html> HTML5 Markup <html> <input type=“color” j:value=“#{colorBean.color2}” /> <input type=“date” j:value=“#{calendarBean.date1}” /> </html>
- 69. Multitenant Capability • JSFapp as a collection of modules – Faces Flows • Modularize behavior • Builds on navigation – Resource Library Contracts • Modularize appearance • Builds on Facelets • Well defined contract for each
- 70. Demo JSF – DeclarativeFlows, Resource Contracts
- 71.
- 72. RichFaces 4.3 • Rich& interactive components • Client-Side Validation • Push
- 76. RichFaces 5.0 • Sneakpeek – Visual Improvements • 3rd-party widget libraries • Skinnability – LESS – Bootstrap 3 – New Components • Charts
- 77. Summary • JSF – Fully-featuredweb framework • JAX-RS – RESTful services • WebSocket – Efficient bi-directional communication • JSON-P – Standardization of JSON processing
- 78.