Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Java EE 7 Development with WildFly

You're reading from   Java EE 7 Development with WildFly Leverage the power of the WildFly application server from JBoss to develop modern Java EE 7 applications

Arrow left icon
Product type Paperback
Published in Dec 2014
Publisher
ISBN-13 9781782171980
Length 434 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Toc

Table of Contents (16) Chapters Close

Preface 1. Getting Started with WildFly FREE CHAPTER 2. Your First Java EE Application on WildFly 3. Introducing Java EE 7 – EJBs 4. Learning Context and Dependency Injection 5. Combining Persistence with CDI 6. Developing Applications with JBoss JMS Provider 7. Adding Web Services to Your Applications 8. Adding WebSockets 9. Managing the Application Server 10. Securing WildFly Applications 11. Clustering WildFly Applications 12. Long-term Tasks' Execution 13. Testing Your Applications A. Rapid Development Using JBoss Forge Index

Summary


In this chapter, we introduced some of the basic web services concepts so that you could get acquainted with these technologies before using them to enhance your ticket application.

Then, we went through SOAP-based web services that are based on a contract between the service and client defined by the WSDL file. SOAP web services are an excellent option to integrate systems when you have well-defined, abstract operations exposed using standard XML files.

Then, we discussed REST services. The key to the REST methodology is to write web services using an interface that is already well known and widely used: the URI. The twist here is to identify the key system resources (this can be entities, collections, or anything else the designer thinks is worthy of having its own URI) and expose them using standard methods that are mapped to standard methods. In this case, the HTTP verbs are mapped to resource-specific semantics.

We created two applications that use our REST API: one console-based...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image