Prompt for the LochApp

Please create a React-JS application for the LochModule. The application  has to offer the following views for the user interface: 
    1. BunkerView 
    2. FairwayView 
    3. GruenView 
    4. LochView 
    5. WasserhindernisView 
The views have to be reachable for the user via a menu list at the left side of each view. The requirements for the 5 views are defined below.

1. The BunkerView must contain the following fields: 
    - name: FlaecheQm   type: LONG 
    - name: IstTopfbunker   type: BOOL 
    - name: Loch   type: Loch 
    - name: PositionBeschreibung   type: STRING 
    - name: Typ   type: STRING 
The data source for the [Loch] select control should be loaded from the relative URL: 
    "/LochService/loch"   (HTTP-GET) 
An existing Bunker entity should be loaded from the relative URL: 
    "/LochService/bunker/{id}"   (HTTP-GET) 
If a new Bunker entity has been created, the new entity should be posted to the relative URL: 
    "/LochService/bunker"   (HTTP-POST) 
If an existing Bunker entity has been updated, the modified entity should be sent to the relative URL: 
    "/LochService/bunker/{id}"   (HTTP-PUT) 
If an existing Bunker entity has to be deleted, the following relative URL should be called: 
    "/LochService/bunker/{id}"   (HTTP-DELETE)

2. The FairwayView must contain the following fields: 
    - name: BreiteMeter   type: LONG 
    - name: GefaelleBeschreibung   type: STRING 
    - name: Grasart   type: STRING 
    - name: HatDogleg   type: BOOL 
    - name: LaengeMeter   type: LONG 
    - name: Loch   type: Loch 
The data source for the [Loch] select control should be loaded from the relative URL: 
    "/LochService/loch"   (HTTP-GET) 
An existing Fairway entity should be loaded from the relative URL: 
    "/LochService/fairway/{id}"   (HTTP-GET) 
If a new Fairway entity has been created, the new entity should be posted to the relative URL: 
    "/LochService/fairway"   (HTTP-POST) 
If an existing Fairway entity has been updated, the modified entity should be sent to the relative URL: 
    "/LochService/fairway/{id}"   (HTTP-PUT) 
If an existing Fairway entity has to be deleted, the following relative URL should be called: 
    "/LochService/fairway/{id}"   (HTTP-DELETE)

3. The GruenView must contain the following fields: 
    - name: FlaecheQm   type: LONG 
    - name: Grasart   type: STRING 
    - name: Loch   type: Loch 
    - name: Mehrstufig   type: BOOL 
    - name: Stimpwert   type: STRING 
    - name: UmgebungBeschreibung   type: STRING 
The data source for the [Loch] select control should be loaded from the relative URL: 
    "/LochService/loch"   (HTTP-GET) 
An existing Gruen entity should be loaded from the relative URL: 
    "/LochService/gruen/{id}"   (HTTP-GET) 
If a new Gruen entity has been created, the new entity should be posted to the relative URL: 
    "/LochService/gruen"   (HTTP-POST) 
If an existing Gruen entity has been updated, the modified entity should be sent to the relative URL: 
    "/LochService/gruen/{id}"   (HTTP-PUT) 
If an existing Gruen entity has to be deleted, the following relative URL should be called: 
    "/LochService/gruen/{id}"   (HTTP-DELETE)

4. The LochView must contain the following fields: 
    - name: Beschreibung   type: STRING 
    - name: Golfplatz   type: Golfplatz 
    - name: LaengeMeter   type: LONG 
    - name: Name   type: STRING 
    - name: Nummer   type: LONG 
    - name: Par   type: LONG 
    - name: Vorgabe   type: LONG 
The data source for the [Golfplatz] select control should be loaded from the relative URL: 
    "/GolfplatzService/golfplatz"   (HTTP-GET) 
An existing Loch entity should be loaded from the relative URL: 
    "/LochService/loch/{id}"   (HTTP-GET) 
If a new Loch entity has been created, the new entity should be posted to the relative URL: 
    "/LochService/loch"   (HTTP-POST) 
If an existing Loch entity has been updated, the modified entity should be sent to the relative URL: 
    "/LochService/loch/{id}"   (HTTP-PUT) 
If an existing Loch entity has to be deleted, the following relative URL should be called: 
    "/LochService/loch/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Rough columns: 
    - column: Grasart 
    - column: Beschreibung 
    - column: Typ 
    - column: Loch 
    - column: Pflegegrad 
The table should have the title "Roughs" und the data must be loaded from the server with the following relative URL: 
    "/GreenkeeperService/rough/loch/{id}" 
Add a HTML table to the view with the following Gruen columns: 
    - column: Loch 
    - column: Stimpwert 
    - column: FlaecheQm 
    - column: Grasart 
    - column: Mehrstufig 
    - column: UmgebungBeschreibung 
The table should have the title "Gruens" und the data must be loaded from the server with the following relative URL: 
    "/LochService/gruen/loch/{id}" 
Add a HTML table to the view with the following Fairway columns: 
    - column: BreiteMeter 
    - column: GefaelleBeschreibung 
    - column: HatDogleg 
    - column: Grasart 
    - column: LaengeMeter 
    - column: Loch 
The table should have the title "Fairways" und the data must be loaded from the server with the following relative URL: 
    "/LochService/fairway/loch/{id}" 
Add a HTML table to the view with the following Abschlag columns: 
    - column: Farbe 
    - column: Name 
    - column: LaengeMeter 
    - column: Geschlecht 
    - column: Loch 
The table should have the title "Abschlags" und the data must be loaded from the server with the following relative URL: 
    "/GreenkeeperService/abschlag/loch/{id}" 
Add a HTML table to the view with the following Bunker columns: 
    - column: Typ 
    - column: FlaecheQm 
    - column: PositionBeschreibung 
    - column: IstTopfbunker 
    - column: Loch 
The table should have the title "Bunkers" und the data must be loaded from the server with the following relative URL: 
    "/LochService/bunker/loch/{id}" 
Add a HTML table to the view with the following Wasserhindernis columns: 
    - column: Typ 
    - column: PositionBeschreibung 
    - column: Geschuetzt 
    - column: Seitlich 
    - column: Loch 
The table should have the title "Wasserhinderniss" und the data must be loaded from the server with the following relative URL: 
    "/LochService/wasserhindernis/loch/{id}"

5. The WasserhindernisView must contain the following fields: 
    - name: Geschuetzt   type: BOOL 
    - name: Loch   type: Loch 
    - name: PositionBeschreibung   type: STRING 
    - name: Seitlich   type: BOOL 
    - name: Typ   type: STRING 
The data source for the [Loch] select control should be loaded from the relative URL: 
    "/LochService/loch"   (HTTP-GET) 
An existing Wasserhindernis entity should be loaded from the relative URL: 
    "/LochService/wasserhindernis/{id}"   (HTTP-GET) 
If a new Wasserhindernis entity has been created, the new entity should be posted to the relative URL: 
    "/LochService/wasserhindernis"   (HTTP-POST) 
If an existing Wasserhindernis entity has been updated, the modified entity should be sent to the relative URL: 
    "/LochService/wasserhindernis/{id}"   (HTTP-PUT) 
If an existing Wasserhindernis entity has to be deleted, the following relative URL should be called: 
    "/LochService/wasserhindernis/{id}"   (HTTP-DELETE)