Java EE 8

JAVA EE 8 UPDATE
Reza Rahman
Ryan Cuprak

Agenda
• Java EE 8 specification overview and current status
• Example of proposed enhancements
• JavaOne 2016 Java EE Reboot
• Java EE 9
• How to get involved and help

Importance of Java EE
https://javaee-guardians.io/java-ee-adoption-surveys

Microservices and Java EE
http://microprofile.io

Java EE: Past, Present, Future
J2EE 1.2
Servlet,
JSP, EJB,
JMS, RMI
J2EE 1.3
CMP,
JCA
J2EE 1.4
Web
Services,
Mgmt,
Deploy
Java EE 5
Ease of
Use,
EJB 3,
JPA, JSF,
JAXB,
JAX-WS
Java EE 6
Pruning,
Ease of
Use,
JAX-RS,
CDI,
Bean-
ValidationWeb Profile
Servlet 3,
EJB 3.1 Lite
Java EE 7
JMS 2,
Batch, TX,
Concurrency
Web-
Sockets,
JSON
Java EE 8
SERVLET 4,
JSON-B,
JSON-P 1.1,
JSF 2.3, CDI
2.0, JAX-
RS 2.1,
SECURITY

Java EE 8 Community Survey
https://java.net/downloads/javaee-spec/JavaEE8_Community_Survey_Results.pdf
https://blogs.oracle.com/ldemichiel/entry/results_from_the_java_ee

Java EE 8 2016 Oracle Survey
http://tinyurl.com/jj853bm

Java EE 8 Overview – Original Plan
• Continued Enhancements for Web Standards Alignment
• HTTP/2, JSON Binding, JSON-P, MVC
• Cloud enhancements
• Security, RESTful Management API
• CDI Programming Model
• Ease of use, EJB via CDI
• Smaller, but Important Features
• Caching, Better Messaging
• Alignment with Java SE 8

Java EE 8 Specifications (Original)
• JMS 2.1
• JAX-RS 2.1
• JSF 2.3
• CDI 2.0
• JSON-P 1.1
• Servlet 4.0
• JCache 1.0
• JSON-B 1.0
• MVC 1.0
• Java EE Security1.0
• Java EE Management 2.0

Java EE 8 Reboot
JSRs proposed to be dropped:
• Management 2.0 (JSR 373)
• JMS 2.1 (JSR 368)
• MVC 1.0 (JSR 371)
Expanded scope:
• Security 1.0 (JSR 375)
Proposed new JSRs:
• Health Checking
• Configuration
New Survey Conducted
Results Not Yet Published
New Target Release
Q4 2017

Servlet 4.0
• Now in public review
• Available in GlassFish 5 and Tomcat 9
JSR 369

Servlet 4.0: HTTP/2
• HTTP/2 Support -> Major Update
• Why do we need HTTP/2?
• Problems with HTTP/1.1:
• Head-of-Line Blocking
• HTTP Pipelining, File Concatenation, & Image Sprites
• Key differences:
• Binary instead of textual
• Fully multiplexed instead of ordered and blocking
• One connection for parallelism
• Uses header compression
• Allows server push
JSR 369

Servlet 4.0: HTTP/2 Support
NOTE: HTTPS only for browsers!

Servlet 4.0
• Principal goal to support HTTP/2
• Request/response multiplexing over single connection
• Transparent to most developers, although possibly slight
changes to the Servlet API
• Most affected: frameworks
JSR 369

Servlet 4.0 – Exposing HTTP./2
• Stream Prioritization
• New Priority class
• Enhance HttpServletRequest and HttpServletResponse to
accommodate
• Server Push
• Frameworks can push resources to the client
• Not replacing WebSockets
JSR 369

JMS 2.1
• JSR 368 - In early stages
• No builds available for testing, as yet.
• Planning: https://java.net/projects/jms-
spec/pages/JMS21Planning
• Proposed to be dropped in EE 8
• New messaging service in EE 9
JSR 368

JMS 2.1
• JMS 2.0 was a major overhaul
• Continuation of API Modernization
• Declarative Message Listeners
• Alternative to MDB
• More Powerful Features
• Available to all Beans
• JMS Provider Portability Improvements
• Dead Message Queues
• Redelivery Behavior on JMS MDB Rollback (delays, max #
consecutive)
JSR 368

JMS 2.1 Asynchronous Batches
In JMS 2.0, messages delivered asynchronously by calling:
javax.jms.MessageListener onMessage(Message message)
Define new
javax.jms.BatchMessageListener onMessages(Message[] messages)
JSR 368

JMS 2.1 Asynchronous Batches
Example:
@MessageDriven
public class MyFlexibleMDB {
@JMSQueueListener(destinationLookup="java:global/
myQueue")
public void myMessageCallback(@Batch(maxSize=10,timeout=
1000) Message[] messages) {
...
}
JSR 368

JMS 2.1 Declarative JMS Listeners
@ApplicationScoped
@MaxConcurrency(10)
public class HandlingEventRegistrationAttemptConsumer {
@JmsListener(
destinationLookup="jms/HandlingEventRegistrationAttemptQueue",
selector="source = 'mobile'",
batchSize=10, retry=5, retryDelay=7000,
orderBy=TIMESTAMP)
@Transactional
public void onEventRegistrationAttempt(
HandlingEventRegistrationAttempt... attempts) {
...
}
}
JSR 368

JAX-RS 2.1
• JSR 370 - In Public Review
• Builds are available
• Reactive API
• Support for SSE (Server Sent Events)
• Integration with JSON-B
JSR 370

JAX-RS 2.1
JSR 370
CompletionStage<String> cs1 = client.target("http://partner.us/api")
.request()
.rx()
.get(String.class);
CompletionStage<String> cs2 = client.target("http://supplier.be/api")
.request()
.rx()
.get(String.class);
// Get both responses in a List (when they are available)
CompletionStage<List<String>> listCompletionStage =
cs1.thenCombine(cs2, Arrays::asList);

JAX-RS 2.1 – Server Sent Events
• Lesser known part of HTML 5
• Server-to-client streaming
• “Stock tickers”, monitoring applications
• Just plain long-lived HTTP
• Between the extremes of vanilla request/response and WebSocket
• Content-type ‘text/event-stream’
• Support via JAX-RS 2.1
• Non-standard API in Jersey

JAX-RS 2.1 – Server Sent Events
@Path("tickers")
public class StockTicker {
@Resource ManagedExecutorService executor;
@GET @Produces("text/event-stream")
public void getQuotes(
@Context SseEventSink sink,
@Context Sse sse) {
executor.execute(() -> {
...
sink.onNext(sse.newEvent(stockqoute));
...
sink.close();
...
});
}
}

JSF 2.3
• JSR 372 - in active progress
• Milestones available for testing
• Read, Test, Supply Feedback
JSR 372

JSF 2.3
• Standardize Web Socket integration
• f:websocket
• Multi-field validation
• Date-time support
• Enhanced CDI Integration
• Lifecycle Enhancements
• PostRenderViewEvent
• EL API Enhancements
• Configuration Enhancements
• AJAX Enhancements
JSR 372

JSF 2.3 Enhanced CDI Integration
Injection of Resources
@Inject
FacesContext facesContext;
@ApplicationMap
@Inject
Map applicationMap;
JSR 372

JSF 2.3 Enhanced CDI Integration
• Wider Support of Injection into JSF Artifacts
• javax.faces.convert.Converter
• javax.faces.validator.Validator
• javax.faces.component.behavior.Behavior
• Upgraded to CDI qualifiers
JSR 372

CDI 2.0
• JSR 365 - in active progress
• Now in public review
• Test Releases of Reference Implementation
http://weld.cdi-spec.org/news/
JSR 374

CDI 2.0
• Java SE Bootstrap
• Asynchronous Events
• Portable Extension SPI Simplification
• Small features and enhancements
JSR 374

CDI Event System Enhancements
• Asynchronous Events
@Inject
private ExperimentalEvent<Configuration> event;
…
event.fireAsync(new Configuration());
• Call to event.fireAsync() returns immediately
JSR 365

CDI 2.0 @Schedule Outside EJB
@ApplicationScoped
public class MyScheduledBean {
...
@Schedule(...)
public void myScheduledTask() { ... }
}
@ApplicationScoped
@Stereotype
@Retention(RUNTIME)
@Target(TYPE)
@Schedule(...)
public @interface MonthlyTask {}
JSR 365

JSON-P 1.1
• JSR 374 - In Public Draft
• More Information:
• https://json-processing-spec.java.net/
• Sources: https://java.net/projects/jsonp
JSR 374

JSON-P 1.1
• Updates to new API in Java EE 7
• New JSON Standards
• JSON-Pointer and JSON-Patch
• Editing Operations on JSON objects and arrays
• Helper Classes and Enhanced Java SE 8 support
JSR 374

JSON-P 1.1 Java SE 8 Support
• Java 8 Stream Support
• JsonArray persons;
persons.getValuesAs(JsonObject.class).stream()
.filter(x->x.getString(“age”) >= 65)
.forEach(System.out.println(x.getString(“name”)));
JSR 374

JSON-P 1.1: JSON-Pointer
JSR 374

JSON-P 1.1: JSON-Patch
public void
shouldBuildJsonPatchExpressionUsingJsonPatchBuilder() {
JsonPatchBuilder patchBuilder = new JsonPatchBuilder();
JsonObject result = patchBuilder.add("/email",
"john@example.com")
.replace("/age", 30)
.remove("/phoneNumber")
.test("/firstName", "John")
.copy("/address/lastName", "/lastName")
.apply(buildPerson());
}
JSR 374

Java EE Management API 2.0
• Oracle dropping JSR from EE 8.
• Java EE Management API 1.0 – released 2002
JSR 373

Java EE Management API 2.0
• REST Based Interface to Supersede EJB Management
APIs of JSR 77
• Monitoring and deployment
• SSE for Event Support (WebSockets also under
consideration)
JSR 373

Bean Validation 2.0
• Add support for LocalTime, Optional, etc.
• Leverage type annotation, repeatable annotations,
reflective parameter name retrieval
• Potential enhancements:
• Customized constraint validations
• Object graph validation
• Example:
List<@Email String> emails;
JSR 380

JPA
@Entity
public class Accident {
@Temporal(TemporalType.TIMESTAMP)
@Past
private Instant when;
}

MVC
• Model - View - Controller
• JSR 371
• Active Progress…download milestones
• Ozark: https://ozark.java.net/
JSR 371

MVC
• Action-Based Web Framework for Java EE
• Follows suit of Spring MVC or Apache Struts
• Does Not Replace JSF
• Model: CDI, Bean Validation, JPA
• View: Facelets, JSP (Extensible)
• Controller: Layered on top of JAX-RS
JSR 371

MVC: Controller Example
@Controller
@Path("/customers")
@View("my-view.jsp")
public class CustomerController {
@Inject
private Models models;
@GET
public String getItems(){
. . .
return “customers.jsp”;
}
JSR 371

MVC: View Example
<c:forEach var="customer" items="${customers}">
<tr>
<td class="text-left">${customer.name}</td>
<td class="text-center">
<form action="${pageContext.request.contextPath}/r/customers/edit"
method="POST">
<input type="hidden" name="id" value="${item.id}"/>
<button type="submit">
Edit
</button>
</form>
</td>
</tr>
</c:forEach>
JSR 371

JSON-B
• Java API for JSON Binding
• JSR 367 - Public Review
• Read the spec, start testing:
https://java.net/projects/jsonb-spec/pages/Home
JSR 367

JSON-B Next Logical Step
• Standardize means of converting JSON to Java objects
and vice versa
• Default mapping algorithm for converting Java classes
• Draw from best of breed ideas in existing JSON binding
solutions
• Provide JAX-RS a standard way to support
“application/json” for POJOs
• JAX-RS currently supports JSON-P
JSR 367

JSON-B Mapping
@Entity public class Person {
@Id String name;
String gender;
@ElementCollection
Map<String, String> phones;
...
}
Person duke = new Person();
duke.setName("Duke");
duke.setGender("Male");
phones = new HashMap<>();
phones.put("home", "650-123-4567");
phones.put("mobile",
"650-234-5678");
duke.setPhones(phones);
{
"name":"Duke",
"gender":"Male",
"phones":{
"home":"650-123-4567",
"mobile":"650-234-5678"
}
}
JSR 367

JSON-B: Proposed Custom Mapping
• Utilization of annotations to map fields to JSON Document Elements
@JsonProperty(“poolType”)
public String poolType;
@JsonPropertyOrder(“poolType”,”shape”)
public class Pool(){
public String poolType;
public String shape;
…
}
{
poolType : “Inground”,
}
{
poolType : “Inground”,
shape : “Rectangle”
}
JSR 367

Java EE Security
• Simplify security for Java EE and improve portability
• Simple security providers
• Database, LDAP
• Simple pluggability
• Universal security context
• Enabling existing security annotations (@RolesAllowed) for all
beans
• EL enabled security annotations via interceptors
• OAuth, OpenID, JWT
• Proposed examples:
• https://github.com/javaee-security-spec/javaee-security-proposals
JSR 367

Java EE Security: Proposed Provider
@DataBaseIdentityStoreDefinition (
dataSourceLookup="java:global/MyDB",
callerQuery=
"SELECT password FROM principals WHERE username=?",
groupsQuery="SELECT role FROM roles where username=?", ...)
@LdapIdentityStoreDefinition (
url="ldap://ds.acme.com:389",
baseDn="dc=acme,dc=com", ...)
JSR 375

Simple Security Plugability
@SecurityProvider
public class MySecurityProvider {
@Inject UserService userService;
@OnAuthentication
// The parameters should suit the credentials mechanism being
// used.
public Principal getPrincipal(
String username, String password) {
// Construct the principal using the user service.
}
@OnAuthorization
public String[] getRoles (Principal principal) {
// Construct an array of roles using the principal and user
// service.
}
}

Security Context Example
@AccessLogged @Interceptor
public class AccessLoggingInterceptor {
@Inject private SecurityContext security;
@AroundInvoke
public Object logMethodAccess(InvocationContext ctx)
throws Exception {
System.out.println("Entering method: "
+ ctx.getMethod().getName());
System.out.println("Current principal: "
+ security.getCallerPrincipal());
System.out.println("User is admin: "
+ security.isCallerInRole("admin"));
return ctx.proceed();
}
}

EL Enabled Security Annotations
@IsAuthorized("hasRoles('Manager') && schedule.officeHours")
public void transferFunds();
@IsAuthorized(
"hasRoles('Manager') && hasAttribute('directReports', employeeId)")
public double getSalary(long employeeId);

JCache
• Java Temporary Caching API
• JSR 107 - Started in 2001
• Provides a common way for Java applications to create,
access, update, and remove entries from caches
JSR 197

JCache
• Provide applications with caching
functionality…particularly the ability to cache Java objects
• Define common set of caching concepts & facilities
• Minimize learning curve
• Maximize portability
• Support in-process and distributed cache implementations
JSR 107

Repeatable Annotations
@NamedQueries({
@NamedQuery(name=SELECT_ALL, query="..."),
@NamedQuery(name=COUNT_ALL, query="...")
})
public class Customer {
...
@NamedQuery(name=SELECT_ALL, query="...")
@NamedQuery(name=COUNT_ALL, query="...")
public class Customer {
...

Java EE Roadmap - JavaOne 2016
2016
• Feedback through Survey
• Launch Java EE Next JSRs
2017
• Java EE 8
• Specs, RI, TCK complete
• Initial microservices support
• Define Java EE 9
• Early access implementation
of Java EE 9
2018
• Java EE 9
• Specs, RI, TCK complete
• Modular Java EE runtime
• Enhanced microservices
support

Java EE 9
• OAuth, OpenID, JWT
• Dynamic configuration
• Fat jars, modularity
• Health check/metrics
• Circuit breakers
• Dynamic discovery
• Client-side load-balancing
• NoSQL
• Multitenancy
• Events
• State management
• Eventual consistency

Java EE: Take Action
• Start working with Java EE 8 today
• Tools:
• GlassFish v5 (or Payara)
• Tomcat 9 web sockets
• Milestones
• Examples and Specification Docs

Java EE Resources
• JavaOne 2016 EE 8 Update/Reboot
• http://tinyurl.com/zeark5t
• Java EE 8 by Arjan Tijms
• https://javaee8.zeef.com/arjan.tijms
• JavaOne 2016 Sessions
• https://www.oracle.com/javaone/
• JSR 366
• https://www.jcp.org/en/jsr/detail?id=366

Join Us!
https://javaee-guardians.io

Adopt-A-JSR
• Started in 2007, easy way for JUGs to get involved
• What you can do depends upon what you want to do &
what spec leads are looking for

Java EE 8

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Java EE 8

Similar to Java EE 8 (20)

More from Ryan Cuprak

More from Ryan Cuprak (12)

Recently uploaded

Recently uploaded (20)

Java EE 8

Editor's Notes