anchor.diff:  While working from JBoss Developer Studio (JBDS), after opening the Forge wizard (Ctrl + 4 or CMD + 4 on Mac), 
   you should choose _JPA: New Entity_ and you'll see a JPA configuration window. This window provides default values for the Java EE container default data-source, but if you not do wish to use it, you can change your configuration as specified before with CLI. 
   
  -In first step you need setup JPA in your project:
  +In the first step you need to setup JPA in your project:
   
   image::../images/using/jpa-setup.png[title="Setup JPA"]
   
  -The next step you need configure your connection settings:
  +The next step you need to configure your connection settings:
   
   image::../images/using/configure-connection-settings.png[title="Configuring Connection Settings"]
   
  
positive.code: --
  
  
  === Scaffolding JSF
  
  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. 
  
  
negative.code: [cdbookstore]$ as-setup --server wildfly8
  ----
  
  Wait a bit until WildFly is downloaded.... (in the meantime you can go to `~/.forge/addons` and have a look at what's happening... you can even check the logs under `~/.forge/log/forge.log`)... ok, now that Wildfly is downloaded into your local Maven directory... there it is.... just type `as`, press `TAB` and you will see new commands : 
  
  [source, console]
  ----
  