Prompt for the GelaendersystemApp

Please create a React-JS application for the GelaendersystemModule. The application  has to offer the following views for the user interface: 
    1. BauteiltypView 
    2. GelaendersystemView 
    3. PylonView 
    4. PylontypView 
The views have to be reachable for the user via a menu list at the left side of each view. The requirements for the 4 views are defined below.

1. The BauteiltypView must contain the following fields: 
    - name: Beschreibung   type: STRING 
    - name: Name   type: STRING 
An existing Bauteiltyp entity should be loaded from the relative URL: 
    "/GelaendersystemService/bauteiltyp/{id}"   (HTTP-GET) 
If a new Bauteiltyp entity has been created, the new entity should be posted to the relative URL: 
    "/GelaendersystemService/bauteiltyp"   (HTTP-POST) 
If an existing Bauteiltyp entity has been updated, the modified entity should be sent to the relative URL: 
    "/GelaendersystemService/bauteiltyp/{id}"   (HTTP-PUT) 
If an existing Bauteiltyp entity has to be deleted, the following relative URL should be called: 
    "/GelaendersystemService/bauteiltyp/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following BrueckenBauteil columns: 
    - column: Gruendungstyp 
    - column: Lagertyp 
    - column: Fahrbahnuebergangstyp 
    - column: Schutzsystem 
    - column: Bauteiltyp 
    - column: Beschreibung 
    - column: Gelaendersystem 
    - column: Bruecke 
    - column: Material 
    - column: Decksystem 
The table should have the title "BrueckenBauteils" und the data must be loaded from the server with the following relative URL: 
    "/MaterialService/brueckenbauteil/bauteiltyp/{id}"

2. The GelaendersystemView must contain the following fields: 
    - name: Beschreibung   type: STRING 
    - name: HoeheMeter   type: STRING 
    - name: Name   type: STRING 
An existing Gelaendersystem entity should be loaded from the relative URL: 
    "/GelaendersystemService/gelaendersystem/{id}"   (HTTP-GET) 
If a new Gelaendersystem entity has been created, the new entity should be posted to the relative URL: 
    "/GelaendersystemService/gelaendersystem"   (HTTP-POST) 
If an existing Gelaendersystem entity has been updated, the modified entity should be sent to the relative URL: 
    "/GelaendersystemService/gelaendersystem/{id}"   (HTTP-PUT) 
If an existing Gelaendersystem entity has to be deleted, the following relative URL should be called: 
    "/GelaendersystemService/gelaendersystem/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following BrueckenBauteil columns: 
    - column: Gruendungstyp 
    - column: Lagertyp 
    - column: Fahrbahnuebergangstyp 
    - column: Schutzsystem 
    - column: Bauteiltyp 
    - column: Beschreibung 
    - column: Gelaendersystem 
    - column: Bruecke 
    - column: Material 
    - column: Decksystem 
The table should have the title "BrueckenBauteils" und the data must be loaded from the server with the following relative URL: 
    "/MaterialService/brueckenbauteil/gelaendersystem/{id}"

3. The PylonView must contain the following fields: 
    - name: Beschreibung   type: STRING 
    - name: Bruecke   type: Bruecke 
    - name: HoeheMeter   type: STRING 
    - name: Material   type: Material 
    - name: Pylontyp   type: Pylontyp 
The data source for the [Pylontyp] select control should be loaded from the relative URL: 
    "/GelaendersystemService/pylontyp"   (HTTP-GET) 
The data source for the [Material] select control should be loaded from the relative URL: 
    "/MaterialService/material"   (HTTP-GET) 
The data source for the [Bruecke] select control should be loaded from the relative URL: 
    "/BrueckeService/bruecke"   (HTTP-GET) 
An existing Pylon entity should be loaded from the relative URL: 
    "/GelaendersystemService/pylon/{id}"   (HTTP-GET) 
If a new Pylon entity has been created, the new entity should be posted to the relative URL: 
    "/GelaendersystemService/pylon"   (HTTP-POST) 
If an existing Pylon entity has been updated, the modified entity should be sent to the relative URL: 
    "/GelaendersystemService/pylon/{id}"   (HTTP-PUT) 
If an existing Pylon entity has to be deleted, the following relative URL should be called: 
    "/GelaendersystemService/pylon/{id}"   (HTTP-DELETE)

4. The PylontypView must contain the following fields: 
    - name: Beschreibung   type: STRING 
    - name: Name   type: STRING 
An existing Pylontyp entity should be loaded from the relative URL: 
    "/GelaendersystemService/pylontyp/{id}"   (HTTP-GET) 
If a new Pylontyp entity has been created, the new entity should be posted to the relative URL: 
    "/GelaendersystemService/pylontyp"   (HTTP-POST) 
If an existing Pylontyp entity has been updated, the modified entity should be sent to the relative URL: 
    "/GelaendersystemService/pylontyp/{id}"   (HTTP-PUT) 
If an existing Pylontyp entity has to be deleted, the following relative URL should be called: 
    "/GelaendersystemService/pylontyp/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Pylon columns: 
    - column: HoeheMeter 
    - column: Bruecke 
    - column: Material 
    - column: Pylontyp 
    - column: Beschreibung 
The table should have the title "Pylons" und the data must be loaded from the server with the following relative URL: 
    "/GelaendersystemService/pylon/pylontyp/{id}"