anchor.diff:  ----
   
   
  -==== JBDS
  -
  -While from the JBDS, after opening the Forge wizard (Ctrl + 4 or CMD + 4 on Mac), 
  -you should choose _JPA: New Entity_ and you'll see a configuration window. 
  -This window come configured with 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.
  +==== JBoss Developer Studio (JBDS)
  +
  +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:
   
   image::using/jpa-setup.png[title="Setup JPA"]
  
positive.code: Field Name: firstName | Type: String
  --
  
  Then you need to have a Many-to-One relationship with `Book`. 
  After opening the Forge wizard (Ctrl + 4 or CMD + 4 on Mac) you should choose _JPA: New Field_ select the _Book_ as Target Entity
  enter _language_ as Field name, select _org.cdbookstore.model.Language_ as Field Type and mark _Many-to-One_ as Relationship Type and click finish:
  
  image::using/new-relationship.png[title="Creating a new relationship"]
  
  You can configure your relationship in next step as well:
  
  image::using/relationship-configuration.png[title="Configuring relationship"]
  
  Forge takes care of all the JPA relational mapping between both entities. +
  Now, on an entity, we can add Bean Validation constraints. After opening the Forge wizard (Ctrl + 4 or CMD + 4 on Mac) you should choose _Constrait: Add_,
  you'll see a configuration window as in first step of the _JPA: New Entity_ that you did before:
  
  image::using/configure-constraint.png[title="Configuring Constraint"]
  
  You should choose the _Generic Java EE_ as Bean Validation provider and checked in Provided by Application Server?. 
  If you don't want the default configuration provided by Application Server you can change your 
  configurations as well. The next step you need choose _org.cdbookstore.model.Book_ as Class:
  
  image::using/add-constraint.png[title="Adding Constraint"]
  
  In next step you need specify what's _Property_ and what's _Constraint_. 
  This case will need add NotNull on _title_ property:
  
  image::using/add-notnull-constraint.png[title="Adding NotNull Constraint"]
  
  You can define if you want on property or on property accessor.
  The next step you can configure _payload_, _groups_ and _message_:
  
  image:using/configure-constraint.png[title="Configuring Constraint"]
  
  click in finish. You need add more two constraints:
  [source]
  --
  Constraint: Past | Property: publicationDate
  
negative.code: [Book.java]$ jpa-new-field --named language --type org.cdbookstore.model.Language
  ----
  
  By default, a JPA field is of type `String`. With the `--type` option we can choose from basic datatypes (`int`, `byte`, `char`…), enum, or from other entities and entity cardinality (One-to-One, One-to-Many, Many-to-One, Many-to-Many). So let's create a new `Author` entity, and add a Many-to-One relationship with `Book` :
  
  [source, console]
  ----
  