Our next task is to create a new book entry or to edit an existing one. The book editor shall consist of a tab panel offering one page for the books meta data like title, author, publisher, and one page for each language, where you can edit a review. It must be possible to switch between these pages without loosing data. Not very hard to imagine, that we need a backing bean living longer than just one request. Continue reading “Conversation Scope”
As stated before, Books is an application, maintained by just one author, who should know about the expected data. Thus, there is no user interface with immediate response after each input or lots of hints. Of course, those features are essential for an application for potentially “unknown” users. Later on, when developing Alumni, we will cover those features in detail. However, a validation is useful to prevent the user from entering data which might not fit the database. Continue reading “Web Development with Java and JSF: Bean Validation”
Ok, we secured our JSF web application by using a JSF form. The user information is still stored in a flat text file. But as stated before, your application server provides more. This lesson, we move forward to GlassFish’s JDBCRealm, which allows you to store the user information within the database. Continue reading “Tutorial web development (with JSF) XV â€“ Security with JDBCRealm”
Now, after we’ve addressed basic log-in with simple file realm, I want to move on by exchanging the authentication method. Remember, this tutorial is about web development with JavaServer Faces. All I showed for container based security so far, is technology entirely independent from JSF. Same applies to simple form log-in. But, it’s possible to embed this into some JSF techniques. And, further on, using programmatic log-in, this is done by the use of JSF. Continue reading “Tutorial web development (with JSF) XIV â€“ Security Part III”
In this part of the security trail, we start with Basic Authentication and fileRealm. For some basic background information, please refer to the former part.
To secure the TinyCalutor, we need to add a security constraint to web.xml. Continue reading “Tutorial web development (with JSF) XIII â€“ Security Part II”