Book Image

Mastering Java EE Development with WildFly

By : Luca Stancapiano
Book Image

Mastering Java EE Development with WildFly

By: Luca Stancapiano

Overview of this book

Packed with rich assets and APIs, Wildfly 10 allows you to create state-of-the-art Java applications. This book will help you take your understanding of Java EE to the next level by creating distributed Java applications using Wildfly. The book begins by showing how to get started with a native installation of WildFly and it ends with a cloud installation. After setting up the development environment, you will implement and work with different WildFly features, such as implementing JavaServer Pages. You will also learn how you can use clustering so that your apps can handle a high volume of data traffic. You will also work with enterprise JavaBeans, solve issues related to failover, and implement Java Message Service integration. Moving ahead, you will be working with Java Naming and Directory Interface, Java Transaction API, and use ActiveMQ for message relay and message querying. This book will also show you how you can use your existing backend JavaScript code in your application. By the end of the book, you’ll have gained the knowledge to implement the latest Wildfly features in your Java applications.
Table of Contents (20 chapters)
5
Working with Distributed Transactions
16
WildFly in Cloud

Creating REST Services

Representational State Transfer (REST) is an architecture for software distributed hypertext systems such as the World Wide Web. The term REST was introduced in 2000 in the doctoral dissertation by one of the principal authors of Hypertext Transfer Protocol (HTTP), Roy Fielding, and was quickly adopted by the developer community on the Internet. The term REST is often used in the sense of describing any simple interface that transmits data over HTTP without an optional layer, such as SOAP or session management via cookies. These two concepts may conflict as well as overlap. You can design any complex software system in accordance with the REST architecture fielding without using HTTP and not interact with the World Wide Web. You can also design a simple XML + HTTP interface that does not conform to the REST principles and instead, follow a Remote Procedure...