In my blog, I publish a list of those books, I wrote a review for. Every book will be displayed in a table with this information:
- Short text
- Reference to my rewiew
These information is written manually and has to be maintained for every category and language. Changing the layout (if more than just CSS) will be a huge effort.
Now, I want to develop a multiligual application for publishing my booklist in an easy manner. One goal is to publish this information from a single soure in diverse categories and / or languages. Every book should be listet in the appropriate category just by assigning this category. The layout may change and should be maintained at a central place to be used for all books.
Continue reading “Tutorial web development (with JSF): Application “BookReview”, Part I”
You may have developed a web application using JSF or other techniques, wich runs on an application server and should be reachable from the internet. You might configure your AppServer, e.g. GlassFish, listening on port 80 directly. Usually it is better to run this behind a HTTP server, which serves static content or provides load balancing. The folowing configuration is an example how to run GlassFish behind an Apach WebServer.
Its using this scenario:
- The application runs on localhost:8080/myapp
- The site is reachable on http://mydomain.net
- The site is hosted on a virtual server
- The complete site is forwared to the AppServer
- The modules mod_proxy.so and mod_proxy_http.so are loaded
Options Indexes FollowSymLinks MultiViews
allow from all
Allow from all
ProxyPass /myapp http://localhost:8080/myapp/
ProxyPassReverse /myapp http://localhost:8080/myapp/
Essential is the config of ProxyPass(Reverse), which forwards the directory (“/myapp”) to the adress of your AppServer (“http://localhost:8080/myapp/”). Please treat this only as an example. For security reasons you may run Apache within your dmz and GlassFish on a different machine behind your firewall.
Maybe I provide a full commented description later on in an future article of my JSF tutorial.
To web development content.
In the last part of this series, we created a second page, which looked similar to the first one. Now, we will put the common parts into a central place. To do this, we’ll create a template, which acts as kind of container for the shared part, which contains some individual information.
As a reminder, here is the souce of tese two pages:
Continue reading “Tutorial web development (with JSF) VI: Templates”
Suppose, you have to store orders in a SQL DBMS. An order consists of header (address, date, number etc.) as well as a variable count oflines (amount, product, price, tax, …). This should be stored in two tables.
Table Order (
Table OrderLine (
To prevent working directy with SQL, you use JPA. Two entity classes, which are annoted.
Continue reading “JPA and legacy database”
The tiny calculator is now functional. After entering the two parameters ans clicking on one of the buttons for the basic arthimetics, you’ll get the result just below the buttons. This is well designed since the usuer usually wants to stay on this site and continues calculating. On the other side, lots of apps exists with quite a couple of pages. For example, think about a booking system or a shop. Finishing a transaction you’ll usually get es confirmation page. I like to demonstrate you something similar: The result od the addition will be presented on a different page. A button “back” leads you back to the calculator’s main page. This is not a very user friendly design, but it’s just to show you a first approach of page nagvigation.
Continue reading “Tutorial web development (with JSF) V: Scene change”