Revert "[Bug #911] Disabling at interface criterion hierarchy while bug is not fixed."

This reverts commit 295912b3c7. Besides
the CriterionType of a Criterion is eagerly loaded. Otherwise when
having child criterions, proxy errors accesing CriterionType were
happening.

navalplanner-business/src/main/java/org/navalplanner/business/resources/entities/CriterionType.java

@@ -146,7 +146,7 @@ public class CriterionType extends IntegrationEntity implements
 
     private String description;
 
-    private Boolean allowHierarchy = false;
+    private Boolean allowHierarchy = true;
 
     private Boolean allowSimultaneousCriterionsPerResource = true;
 

navalplanner-business/src/main/resources/org/navalplanner/business/resources/entities/Resources.hbm.xml

@@ -113,7 +113,7 @@
     <property access="field" name="predefinedCriterionInternalName" not-null="false"
         column="predefined_criterion_internal_name" />
     <property access="field" name="active"/>
-    <many-to-one access="field" name="type" column="id_criterion_type" not-null="true" />
+    <many-to-one access="field" name="type" lazy="false" column="id_criterion_type" not-null="true" />
 
     <!--  Indexed. It is probable to navigate from a criterion
     to its children criteria -->

navalplanner-webapp/src/main/webapp/resources/criterions/_edition.zul

@@ -53,8 +53,7 @@
                             <label value="${i18n:_('Hierarchy')}" />
                             <checkbox id="cbHierarchy"
                                     checked="@{controller.criterionType.allowHierarchy}"
-                                    onCheck="controller.confirmDisabledHierarchy()"
-                                    disabled="true" />
+                                    onCheck="controller.confirmDisabledHierarchy()" />
                         </row>
                         <row>
                             <label value="${i18n:_('Enabled')}" />