Skip to main content

1. Defining the goals of our application

0. Introducction

First, we have a simple and standard login page.

+-------------------------------+
|           LOGIN PAGE          |
|                               |
|          +-----------------+  |
| user:    |                 |  |
|          +-----------------+  |
|          +-----------------+  |
| password:|                 |  |
|          +-----------------+  |
+-------------------------------+
Now we need a simple dashboard for interacting with the user.

+------------------------------------------------------------+
|        TOP MENU (Selection of the application) [1]         |
+----------------+-------------------------------------------+
|                |                                           |    
|   SELECTED     |  RESULT OF THE SELECTED MENU ACTION       |    
|  APPLICATION   |  (Usually an interactive form)            |
|     MENU       |                                           |    
|                |                                           |
|      [2]       |               [3]                         |
|                |                                           |
|                |                                           |
+----------------+-------------------------------------------+

We can have multiple applications, (for instance an application for production, another for bank accounts etc.) The top menu [1] selects our application.
For each application, we have a special menu for it. It is in the selected application menu [2].
After selecting a menu option from the selected application menu, usually, a form is displayed [3].

But a menu item can represent several types of actions (Not only forms):

  1. CRUD form
  2. Report
  3. Query form
  4. Configuration FORM
  5. An outer URL 
  6. Execute a bean method.

Other kind of user interface can be defined (pop-up windows, tabs etc)
Now we need a simple dashboard for our application


Comments

Post a Comment

Popular posts from this blog

10. JSF How to access my resources files?

Sometimes it is really difficult to access any resources form different Java applications. So let's see some scenarios: 1. Executable jar application in a NO WEB environment. Take into account that this is not a JSF application !!! It is desired to have a property file outside the "jar file" so that we can change properties when needed. For instance, we will place the properties file in the same folder that the "jar file" lies. To access the folder where the jar is, the trick is to access the folder where the compiled classed are placed and scale 3 folders . (Oh! rather strange, if anybody knows a better idea.., he will be welcome). Here is a simple code. The name of the class containing the code is ThisClass, and we have created a Property class that feeds with a file in the same folder that the" jar file" 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 /** * Gets the folder where resides the executable...
Post a Comment
Read more

9. JSF: Solving common problems

1. Target Unreachable, identifier [bean] resolved to null When you reference a bean in a xhtml file with "#{bean.method}" and get this error, you should verify that: The bean implements Serializable . The references (javax.servlet-api.4.0.0, javax.faces.2.3.3,  javax.el.api.3.0.1, org.primefaces.6.1) have been selected in your pom.xml You have created the files bean.xml and faces-config.xml in the webapp/WEB-INF folder You have used the correct annotations from CDI  (javax.inject.Named and javax.enterprise.context.SessionScoped, ...) and not ManagedBean or jsf2.2 scopes. 2. Bean declaring a passivating scope must be passivation capable This error causes server not starting and fills up the console with long chained exceptions. It is very annoying. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 SEVERE: A child container failed during start java.util.concurrent.ExecutionException: org.apache.catalina.LifecycleException: Failed to star...
Post a Comment
Read more

2. Create a Maven JSF project and a simple login page

Updated on Oct-25-2107 0. Introduction Remember to install previously: Java JDK 8 Eclipse Oxygen Lombok  Apache Tomcat 9 1. Create a Maven Project In the top menu select : File - New - Maven Project Press Next Now fill the next form as follows It is important to select: Group id: org.ximodante.jsf  (or another packet you like) Packaging: war Artifact Id and Name: JSFv02 or any name for the project Press Finish 2. The pom.xml file Eclipse complains about the simple generated file. It seems that a web.xml is required if the packaging is selected to war. The simple generated file is  1 2 3 4 5 6 7 8 9 <project xmlns= "http://maven.apache.org/POM/4.0.0" xmlns:xsi= "http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation= "http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd" > <modelVersion> 4.0.0 </modelVersion> <groupId> org.ximodante...
Post a Comment
Read more