Book Image

Getting Started with Oracle WebLogic Server 12c: Developer's Guide

Book Image

Getting Started with Oracle WebLogic Server 12c: Developer's Guide

Overview of this book

Oracle WebLogic server has long been the most important, and most innovative, application server on the market. The updates in the 12c release have seen changes to the Java EE runtime and JDK version, providing developers and administrators more powerful and feature-packed functionalities. Getting Started with Oracle WebLogic Server 12c: Developer's Guide provides a practical, hands-on, introduction to the application server, helping beginners and intermediate users alike get up to speed with Java EE development, using the Oracle application server. Starting with an overview of the new features of JDK 7 and Java EE 6, Getting Started with Oracle WebLogic Server 12c quickly moves on to showing you how to set up a WebLogic development environment, by creating a domain and setting it up to deploy the application. Once set up, we then explain how to use the key components of WebLogic Server, showing you how to apply them using a sample application that is continually developed throughout the chapters. On the way, we'll also be exploring Java EE 6 features such as context injection, persistence layer and transactions. After the application has been built, you will then learn how to tune its performance with some expert WebLogic Server tips.
Table of Contents (18 chapters)
Getting Started with Oracle WebLogic Server 12c: Developer's Guide
Credits
About the Authors
About the Reviewers
www.PacktPub.com
Preface
Index

Organizing projects in Eclipse


The application architecture points to two isolated modules: the central module, which we will name Store and a remote module that each theater must set up and run at its own installation, aptly named Theater. So, it is a natural decision to have two projects, each implementing one module.

These two modules will be implemented as web applications, holding screens, web services, and business logic. The business entities will reside in projects of their own. This is a common pattern when mapping domain entities that virtually any project of your company will have to access at some point in time. In the development phase, this approach helps avoiding concurrency between developers editing source code and isolates sensitive code if security is a concern. When the systems are up and running, maintenance is also simplified. Instead of repackaging every module that uses the common library, just one update is necessary.

Our entities are mostly isolated by modules,...