• The client API is now part of the specification, so the usage of third-party librar-
ies is no longer needed. The implementation of the specification is required to
provide a REST client that conforms to the common API.
• Asynchronous requests are now supported so that the client does not have to pass-
ively wait for the completion of the task.
• Filters and handlers have been introduced as a common mechanism to provide ex-
tension points for the developer. They can be used for cross-cutting concerns,
such as auditing and security.
• Bean Validation has been integrated into JAX-RS, making constraint annotations
usable for request parameters.
WildFly comes bundled with RESTEasy, an implementation of JAX-RS 2.0.
Java Message Service 2.0 - JSR 343
The JSR 343 is the first update for the JMS specification in over a decade. Once more, the
main theme of the update is the simplification of the API. The new API dramatically de-
creases the amount of boilerplate code that has to be written by the programmer while still
maintaining backwards compatibility. Other new features are listed as follows:
• Asynchronous message sending is now supported, so the application does not
have to be blocked until an acknowledgment from the server is received
• Messages can now be sent with a scheduled delay for the delivery
HornetQ is the JMS provider used and developed by JBoss. It is possible to use it outside
of WildFly as a standalone message broker.
Bean Validation 1.1 - JSR 349
The process of updating the Bean Validation in Java EE 7 concentrates on two main fea-
• Methods validation, which allows the developer to validate parameters and return
• Tighter CDI integration, which changes the life cycle of the elements of the valid-
ation framework, allowing the developer to use dependency injection in his or her
own ConstraintValidator implementations