Part 2: Taking care of constraint validation It takes care of only one object type ( Book) and supports the four standard data management operations ( Create/ Read/ Update/ Delete), but it needs to be enhanced by styling the user interface with CSS rules, and by adding further important parts of the app's overall functionality: The minimal version of a Java back-end data management app discussed in this tutorial only includes a minimum of the overall functionality required for a complete app. In the case of a Java/JPA/JSF back-end app, the back-end part of the app can be executed by a server machine that runs a web server supporting the Java EE specifications Java Servlets, Java Expression Language (EL), JPA and JSF, such as the open source server Tomcat/TomEE. Normally, a distributed web app can be accessed by multiple users, possibly at the same time, over HTTP connections. A back-end web app is a distributed web app where essentially all work is performed by the back-end component, including data validation and UI page creation, while the front-end only consists of a web browser's rendering of HTML-forms-based UI pages. If you first want to see how it works and how it looks like, you can run the minimal app discussed in this article from our server.Ī distributed web app is composed of at least two parts: a front-end part, which, at least, renders the user interface (UI) pages, and a back-end part, which, at least, takes care of persistent data storage. It shows how to build a Java back-end app with minimal effort, using Java Server Faces (JSF) as the user interface technology, the Java Persistence API (JPA) for object-to-storage mapping, and a MySQL database. This article has been extracted from the book Building Back-End Web Apps with Java, JPA and JSF, which is available as an open access online book.
0 kommentar(er)
