Prompt for the HabitatKonzeptApp

Please create a React-JS application for the HabitatKonzeptModule. The application  has to offer the following views for the user interface: 
    1. HabitatKonzeptView 
    2. ZooArchitekturmerkmalView 
    3. ZooHabitatKonzeptNutzungView 
The views have to be reachable for the user via a menu list at the left side of each view. The requirements for the 3 views are defined below.

1. The HabitatKonzeptView must contain the following fields: 
    - name: Beschreibung   type: STRING 
    - name: ErstNutzungJahr   type: LONG 
    - name: Name   type: STRING 
    - name: Ursprungsland   type: STRING 
An existing HabitatKonzept entity should be loaded from the relative URL: 
    "/HabitatKonzeptService/habitatkonzept/{id}"   (HTTP-GET) 
If a new HabitatKonzept entity has been created, the new entity should be posted to the relative URL: 
    "/HabitatKonzeptService/habitatkonzept"   (HTTP-POST) 
If an existing HabitatKonzept entity has been updated, the modified entity should be sent to the relative URL: 
    "/HabitatKonzeptService/habitatkonzept/{id}"   (HTTP-PUT) 
If an existing HabitatKonzept entity has to be deleted, the following relative URL should be called: 
    "/HabitatKonzeptService/habitatkonzept/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following ZooHabitatKonzeptNutzung columns: 
    - column: Notizen 
    - column: Zoo 
    - column: ErstesGehege 
    - column: HabitatKonzept 
The table should have the title "ZooHabitatKonzeptNutzungs" und the data must be loaded from the server with the following relative URL: 
    "/HabitatKonzeptService/zoohabitatkonzeptnutzung/habitatkonzept/{id}"

2. The ZooArchitekturmerkmalView must contain the following fields: 
    - name: Baujahr   type: LONG 
    - name: Beschreibung   type: STRING 
    - name: IstDenkmalschutz   type: BOOL 
    - name: MerkmalTyp   type: STRING 
    - name: Name   type: STRING 
    - name: Zoo   type: Zoo 
The data source for the [Zoo] select control should be loaded from the relative URL: 
    "/ZooService/zoo"   (HTTP-GET) 
An existing ZooArchitekturmerkmal entity should be loaded from the relative URL: 
    "/HabitatKonzeptService/zooarchitekturmerkmal/{id}"   (HTTP-GET) 
If a new ZooArchitekturmerkmal entity has been created, the new entity should be posted to the relative URL: 
    "/HabitatKonzeptService/zooarchitekturmerkmal"   (HTTP-POST) 
If an existing ZooArchitekturmerkmal entity has been updated, the modified entity should be sent to the relative URL: 
    "/HabitatKonzeptService/zooarchitekturmerkmal/{id}"   (HTTP-PUT) 
If an existing ZooArchitekturmerkmal entity has to be deleted, the following relative URL should be called: 
    "/HabitatKonzeptService/zooarchitekturmerkmal/{id}"   (HTTP-DELETE)

3. The ZooHabitatKonzeptNutzungView must contain the following fields: 
    - name: ErstesGehege   type: STRING 
    - name: HabitatKonzept   type: HabitatKonzept 
    - name: Notizen   type: STRING 
    - name: Zoo   type: Zoo 
The data source for the [HabitatKonzept] select control should be loaded from the relative URL: 
    "/HabitatKonzeptService/habitatkonzept"   (HTTP-GET) 
The data source for the [Zoo] select control should be loaded from the relative URL: 
    "/ZooService/zoo"   (HTTP-GET) 
An existing ZooHabitatKonzeptNutzung entity should be loaded from the relative URL: 
    "/HabitatKonzeptService/zoohabitatkonzeptnutzung/{id}"   (HTTP-GET) 
If a new ZooHabitatKonzeptNutzung entity has been created, the new entity should be posted to the relative URL: 
    "/HabitatKonzeptService/zoohabitatkonzeptnutzung"   (HTTP-POST) 
If an existing ZooHabitatKonzeptNutzung entity has been updated, the modified entity should be sent to the relative URL: 
    "/HabitatKonzeptService/zoohabitatkonzeptnutzung/{id}"   (HTTP-PUT) 
If an existing ZooHabitatKonzeptNutzung entity has to be deleted, the following relative URL should be called: 
    "/HabitatKonzeptService/zoohabitatkonzeptnutzung/{id}"   (HTTP-DELETE)