112815 java ee8_davidd

Copyright © 2015, Oracle and/or its affiliates. All rights reserved.
Java EE 8 - Work in Progress
David Delabassee
@delabassee
Oracle Corporation
JJUG CCC 2015 Fall

Safe Harbor Statement
The following is intended to outline our general product direction. It is intended for
information purposes only, and may not be incorporated into any contract. It is not a
commitment to deliver any material, code, or functionality, and should not be relied upon
in making purchasing decisions. The development, release, and timing of any features or
functionality described for Oracle’s products remains at the sole discretion of Oracle.
2

Program Agenda
Quick recap of goals and themes of Java EE 8
What we have accomplished
How you can get involved
1
2
3
3

Industry Trends
Cloud
4

Java EE 8 – Driven by Community Feedback
http://glassfish.org/survey
5

Java EE 8 Themes
• HTML5 / Web Tier Enhancements
• Ease of Development
• Infrastructure for running in the Cloud
6

HTML5 Support / Web Tier Enhancements
• JSON Binding
• JSON Processing enhancements
• Server-sent events
• Action-based MVC
• HTTP/2 support
7

JSON-B 1.0
• API to marshal/unmarshal Java objects to/from JSON
– Similar to JAXB runtime API in XML world
• Draw from best practices of existing JSON binding implementations
– MOXy, Jackson, GSON, Genson, Xstream, …
– Allow switch of JSON binding providers
• Default mapping of classes to JSON
– Annotations to customize the default mappings
– JsonbProperty, JsonbTransient, JsonbNillable, JsonbValue, …
Java API for JSON Binding
8

JSON-B 1.0
@Entity public class Person {
@Id String name;
String gender;
@ElementCollection Map<String,String> phones;
... // getters and setters
}
Person duke = new Person();
duke.setName("Duke");
duke.setGender("M");
phones = new HashMap<String,String>();
phones.put("home", "650-123-4567");
phones.put("mobile", "650-234-5678");
duke.setPhones(phones);
Jsonb jsonb = JsonbBuilder.create();
String person = jsonb.toJson(duke);
{
"name":"Duke",
"gender":"M",
"phones":{
"home":"650-123-4567",
"mobile":"650-234-5678"}
}
9

JSON-P 1.1
• Keep JSON-P spec up-to-date
• Track new standards
• Add editing operations to JsonObject and JsonArray
• Helper classes and methods to better utilize SE 8’s stream operations
Java API for JSON Processing
10

JSON-P 1.1
• JSON-Pointer – IETF RFC 6901
– String syntax for referencing a value
"/0/phones/mobile"
Tracking new standards
11

JSON-P 1.1
JsonArray contacts = ...;
JsonPointer p =
new JsonPointer("/0/phones/mobile");
JsonValue v = p.getValue(contacts);
[
{
"name":"Duke",
"gender":"M",
"phones":{
"home":"650-123-4567",
"mobile":"650-234-5678"}},
{
"name":"Jane",
"gender":"F",
"phones":{
"mobile":"707-555-9999"}}
]
12

JSON-P 1.1
JsonPointer p =
JsonArray newContacts =
p.replace(contacts, "650-555-1234");
[
{
"name":"Duke",
"gender":"M",
"phones":{
"home":"650-123-4567",
"mobile":"650-234-5678"}},
{
"name":"Jane",
"gender":"F",
"phones":{
"mobile":"707-555-9999"}}
]
13

JSON-P 1.1
JsonPointer p =
JsonArray newContacts =
p.replace(contacts, "650-555-1234");
[
{
"name":"Duke",
"gender":"M",
"phones":{
"home":"650-123-4567",
"mobile":"650-555-1234"}},
{
"name":"Jane",
"gender":"F",
"phones":{
"mobile":"707-555-9999"}}
]
14

JSON-P 1.1
• JSON-Patch – IETF RFC 6902
• Patch is a JSON document
– Array of objects / operations for modifying a JSON document
– add, replace, remove, move, copy, test
– Must have "op" field and "path" field
[
{"op":"replace", "path":"/0/phones/mobile", "value":"650-111-2222"},
{"op":"remove", "path":"/1"}
]
Tracking new standards
15

JSON-P 1.1
JSON Query using Streams API
List<String> femaleNames = contacts.getValuesAs(JsonObject.class).stream()
.filter(x->"F".equals(x.getString("gender")))
.map(x->(x.getString("name"))
.collect(Collectors.toList());
JsonArray femaleNames = contacts.getValuesAs(JsonObject.class).stream()
.filter(x->"F".equals(x.getString("gender")))
.map(x->(x.getString("name"))
.collect(JsonCollectors.toJsonArray());
16

Server-sent Events
• Part of HTML5 standardization
• Server-to-client streaming of text data
• Mime type is text/event-stream
• Long-lived HTTP connection
– Client establishes connection
– Server pushes update notifications to client
– Commonly used for one-way transmission for period updates or updates due to
events
17

Server-sent Events
• JAX-RS a natural fit
– Streaming HTTP resources already supported
– Small extension
• Server API: new media type; EventOutput
• Client API: new handler for server side events
– Convenience of mixing with other HTTP operations; new media type
– Jersey (JAX-RS RI) already supports SSE
18

Server-sent Events
@Path("tickers")
public class StockTicker {
@Get
@Produces("text/event-stream")
public EventOutput getQuotes() {
EventOutput eo = new EventOutput();
new StockThread(eo).start();
return eo;
}
}
JAX-RS resource class
19

Server-sent Events
JAX-RS StockThread class
class StockThread extends Thread {
private EventOutput eo;
private AtomicBoolean ab =
new AtomicBoolean(true);
public StockThread(EventOutput eo) {
this.eo = eo;
}
public void terminate() {
ab.set(false);
}
@Override
public void run() {
while (ab.get()) {
try {
// ...
eo.send(new StockQuote("..."));
// ...
} catch (IOException e) {
// ...
}
}
}
}
20

Server-sent Events
WebTarget target = client.target("http://example.com/tickers");
EventSource eventSource = new EventSource(target) {
@Override
public void onEvent(InboundEvent inboundEvent) {
StockQuote sq = inboundEvent.readData(StockQuote.class);
// ...
}
};
eventSource.open();
JAX-RS Client
21

Model View Controller (MVC)
• Component-based MVC
– Controller provided by the framework
– JSF, Wicket, Tapestry…
• Action-based MVC
– Controllers defined by the application
– Struts 2, Spring MVC…
2 Styles
22

MVC 1.0
• Action-based model-view-controller architecture
• Glues together key Java EE technologies:
– Model
• CDI, Bean Validation, JPA
– View
• Facelets, JSP
– Controller
• JAX-RS resource methods
23

MVC 1.0
@Path("hello")
public class HelloController {
@Inject
private Greeting greeting;
@GET
@Controller
public String hello() {
greeting.setMessage("Hello Tokyo!");
return "hello.jsp";
}
}
Model Controller
@Named
@RequestScoped
public class Greeting {
private String message;
public String getMessage() {
return message;
}
public void setMessage(message) {
this.message = message;
}
}
24

MVC 1.0
<%@ page contentType="text/html;charset=UTF-8" language="java" %>
<html>
<head>
<title>Hello</title>
</head>
<body>
<h1>${greeting.message}</h1>
</body>
</html>
View
25

HTTP/2
• HTTP 1.1 uses TCP poorly
– HTTP flows are short and bursty
– TCP was built for long-lived flows
• Workarounds
– Sprites
– Domain sharding
– Inlining
– File concatenation
Address the Limitations of HTTP 1.x
26

HTTP/2
HTTP/2 Goals
• Reduce latency
• Address the HOL blocking problem
• Support parallelism (without requiring multiple connections)
• Define interaction with HTTP 1.x
• Retain semantics of HTTP 1.1
Address the Limitations of HTTP 1.x
27

HTTP/2
• Binary Framing
• Request/Response multiplexing over single connection
– Fully bidirectional
– Multiple streams
• Server Push
• Header Compression
• Upgrade from HTTP 1.1
• Stream Prioritization
Features
28

Servlet 4.0
• Binary Framing
• Request/Response multiplexing
– Servlet Request as HTTP/2 message
• Upgrade from HTTP 1.1
• Server Push
• Stream prioritization
HTTP/2 Features in Servlet API
29

Ease of Development
• CDI alignment
• Security interceptors
• Simplified messaging with JMS message-driven beans
• JAX-RS injection alignment
• WebSocket scopes
• Pruning of EJB 2.x client view and IIOP interoperability
30

Java EE Security 1.0
@IsAuthorized("hasRoles('Manager') && schedule.officeHrs")
void transferFunds()
@IsAuthorized("hasRoles('Manager') && hasAttribute('directReports', employee.id)")
double getSalary(long employeeId);
@IsAuthorized(ruleSourceName="java:app/payrollAuthRules", rule="report")
void displayReport();
Authorization via CDI Interceptors
31

JMS 2.1
• Continue the ease-of-use improvements started in JMS 2.0
• Improve the API for receiving messages asynchronously
– Improve JMS MDBs
– Provide alternative to JMS MDBs
New API to receive messages asynchronously
32

CDI 2.0
• Modularity
• Java SE support
• Asynchronous Events
• Event ordering
• …
33

Modernize the Infrastructure
• Java EE Management 2.0
– REST-based APIs for Management and Deployment
• Java EE Security 1.0
– Authorization
– Password Aliasing
– User Management
– Role Mapping
– Authentication
– REST Authentication
For On-Premise and for in the Cloud
34

Java EE 8 JSRs
• Java EE 8 Platform (JSR 366)
• CDI 2.0 (JSR 365)
• JSON Binding 1.0 (JSR 367)
• JMS 2.1 (JSR 368)
• Java Servlet 4.0 (JSR 369)
• JAX-RS 2.1 (JSR 370)
• MVC 1.0 (JSR 371)
• JSF 2.3 (JSR 372)
• Java EE Management 2.0 (JSR 373)
• JSON-P 1.1 (JSR 374)
• Java EE Security 1.0 (JSR 375)
35

Expected MRs and small JSRs
• Connector Architecture
• WebSocket
• Interceptors
• JPA
• EJB
• JTA
• Bean Validation
• Batch
• JavaMail
• …
36

Transparency
• Our Java EE 8 JSRs run in the open on java.net
– http://javaee-spec.java.net
– One project per JSR – jax-rs-spec, mvc-spec, servlet-spec,…
– https://java.net/projects/javaee-spec/pages/Specifications
• Publically viewable Expert Group mail archive
– Users observer lists gets all copies
• Publicly accessible download area
• Publicly accessible issue tracker / JIRA
• …
Commitment to JCP transparent processes
37

How to Get Involved
• Join an Expert Group project
– http://javaee-spec.java.net
– https://java.net/projects/javaee-spec/pages/Specifications
• Adopt a JSR
– http://glassfish.org/adoptajsr
• The Aquarium
– http://blogs.oracle.com/theaquarium
• Java EE 8 Reference Implementation
– http://glassfish.org
38

112815 java ee8_davidd

Recommended

More Related Content

What's hot (20)

Viewers also liked (18)

Similar to 112815 java ee8_davidd (20)

More from Takashi Ito (7)

Recently uploaded (20)

112815 java ee8_davidd