anchor.diff:  
   image::../images/using/add-constraint.png[title="Adding Constraint"]
   
  -In next step you need specify the property on which to operate _Property_ and the _Constraint_ to configure. 
  -In this case, let's add NotNull on _title_ property:
  +In the next step you need to specify the property _Property_ and the _Constraint_ to configure. 
  +In this case, let's add @NotNull on the _title_ property:
   
   image::../images/using/add-notnull-constraint.png[title="Adding NotNull Constraint"]
   
  
positive.code: 
  If you have executed the `jpa-setup` command, you've noticed that the prompt has changed: you went from `[cdbookstore]` to `[persistence.xml]`. In Forge, the prompt always tells you where you are. You can even enter the command `pwd` or `ls`. For now, let's go back into the `Book` entity: enter `cd~~` brings you to the root directory, and then `cd src/main/java/org/cdbookstore/model/Book.java`. 
  
  So, let's create a few fields in the `Book` entity. Again, one single command end Forge will do its best to simplify our lives :
  
  [source, console]
  ----
  
negative.code: --
  
  
  === Scaffolding JSF (Java Server Faces)
  
  JSF is the default Java EE user interface framework, and consequently JBoss Forge has a great support for it. In fact, Forge can scaffold an entire CRUD web application from JPA entities very easily, with only a single command. The JSF generated application follows several patterns and best practices: usage of CDI conversation scope, the extended persistence context, JSF converters and so on. If you don't believe it, just try it. 
  
  