Prompt for the BrueckeApp

Please create a React-JS application for the BrueckeModule. The application  has to offer the following views for the user interface: 
    1. BrueckeView 
    2. SeilView 
    3. SeiltypView 
    4. WasserlaufView 
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 BrueckeView must contain the following fields: 
    - name: AnzahlFelder   type: LONG 
    - name: Baujahr   type: LONG 
    - name: Beschreibung   type: STRING 
    - name: BeweglichesBrueckensystem   type: BeweglichesBrueckensystem 
    - name: BreiteMeter   type: STRING 
    - name: Eroeffnung   type: LONG 
    - name: HauptspannweiteMeter   type: STRING 
    - name: IstBeweglich   type: BOOL 
    - name: LaengeMeter   type: STRING 
    - name: LichtraumhoeheMeter   type: STRING 
    - name: Material   type: Material 
    - name: Name   type: STRING 
    - name: Ort   type: Ort 
    - name: Tragwerkssystem   type: Tragwerkssystem 
    - name: Wasserlauf   type: Wasserlauf 
The data source for the [Ort] select control should be loaded from the relative URL: 
    "/OrtService/ort"   (HTTP-GET) 
The data source for the [Wasserlauf] select control should be loaded from the relative URL: 
    "/BrueckeService/wasserlauf"   (HTTP-GET) 
The data source for the [BeweglichesBrueckensystem] select control should be loaded from the relative URL: 
    "/GruendungstypService/beweglichesbrueckensystem"   (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 [Tragwerkssystem] select control should be loaded from the relative URL: 
    "/TragwerkssystemService/tragwerkssystem"   (HTTP-GET) 
An existing Bruecke entity should be loaded from the relative URL: 
    "/BrueckeService/bruecke/{id}"   (HTTP-GET) 
If a new Bruecke entity has been created, the new entity should be posted to the relative URL: 
    "/BrueckeService/bruecke"   (HTTP-POST) 
If an existing Bruecke entity has been updated, the modified entity should be sent to the relative URL: 
    "/BrueckeService/bruecke/{id}"   (HTTP-PUT) 
If an existing Bruecke entity has to be deleted, the following relative URL should be called: 
    "/BrueckeService/bruecke/{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/bruecke/{id}" 
Add a HTML table to the view with the following Feld columns: 
    - column: Reihenfolge 
    - column: Bruecke 
    - column: Feldrolle 
    - column: LaengeMeter 
The table should have the title "Felds" und the data must be loaded from the server with the following relative URL: 
    "/LagertypService/feld/bruecke/{id}" 
Add a HTML table to the view with the following BrueckeVerkehrsart columns: 
    - column: Verkehrsart 
    - column: Bruecke 
The table should have the title "BrueckeVerkehrsarts" und the data must be loaded from the server with the following relative URL: 
    "/GruendungstypService/brueckeverkehrsart/bruecke/{id}" 
Add a HTML table to the view with the following BrueckeLagekategorie columns: 
    - column: Lagekategorie 
    - column: Bruecke 
The table should have the title "BrueckeLagekategories" und the data must be loaded from the server with the following relative URL: 
    "/TragwerkssystemService/brueckelagekategorie/bruecke/{id}" 
Add a HTML table to the view with the following BrueckeFunktionskategorie columns: 
    - column: Bruecke 
    - column: Funktionskategorie 
The table should have the title "BrueckeFunktionskategories" und the data must be loaded from the server with the following relative URL: 
    "/OrtService/brueckefunktionskategorie/bruecke/{id}" 
Add a HTML table to the view with the following Seilsystem columns: 
    - column: Beschreibung 
    - column: Systemtyp 
    - column: Bruecke 
The table should have the title "Seilsystems" und the data must be loaded from the server with the following relative URL: 
    "/LagertypService/seilsystem/bruecke/{id}" 
Add a HTML table to the view with the following Seil columns: 
    - column: LaengeMeter 
    - column: Seiltyp 
    - column: Bruecke 
    - column: Seilsystem 
    - column: Beschreibung 
    - column: DurchmesserMillimeter 
The table should have the title "Seils" und the data must be loaded from the server with the following relative URL: 
    "/BrueckeService/seil/bruecke/{id}" 
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/bruecke/{id}" 
Add a HTML table to the view with the following BrueckenEigentum columns: 
    - column: Bruecke 
    - column: Eigentuemer 
    - column: AnteilProzent 
    - column: Eigentumsart 
The table should have the title "BrueckenEigentums" und the data must be loaded from the server with the following relative URL: 
    "/EigentuemerService/brueckeneigentum/bruecke/{id}"

2. The SeilView must contain the following fields: 
    - name: Beschreibung   type: STRING 
    - name: Bruecke   type: Bruecke 
    - name: DurchmesserMillimeter   type: STRING 
    - name: LaengeMeter   type: STRING 
    - name: Seilsystem   type: Seilsystem 
    - name: Seiltyp   type: Seiltyp 
The data source for the [Seilsystem] select control should be loaded from the relative URL: 
    "/LagertypService/seilsystem"   (HTTP-GET) 
The data source for the [Bruecke] select control should be loaded from the relative URL: 
    "/BrueckeService/bruecke"   (HTTP-GET) 
The data source for the [Seiltyp] select control should be loaded from the relative URL: 
    "/BrueckeService/seiltyp"   (HTTP-GET) 
An existing Seil entity should be loaded from the relative URL: 
    "/BrueckeService/seil/{id}"   (HTTP-GET) 
If a new Seil entity has been created, the new entity should be posted to the relative URL: 
    "/BrueckeService/seil"   (HTTP-POST) 
If an existing Seil entity has been updated, the modified entity should be sent to the relative URL: 
    "/BrueckeService/seil/{id}"   (HTTP-PUT) 
If an existing Seil entity has to be deleted, the following relative URL should be called: 
    "/BrueckeService/seil/{id}"   (HTTP-DELETE)

3. The SeiltypView must contain the following fields: 
    - name: Beschreibung   type: STRING 
    - name: Name   type: STRING 
An existing Seiltyp entity should be loaded from the relative URL: 
    "/BrueckeService/seiltyp/{id}"   (HTTP-GET) 
If a new Seiltyp entity has been created, the new entity should be posted to the relative URL: 
    "/BrueckeService/seiltyp"   (HTTP-POST) 
If an existing Seiltyp entity has been updated, the modified entity should be sent to the relative URL: 
    "/BrueckeService/seiltyp/{id}"   (HTTP-PUT) 
If an existing Seiltyp entity has to be deleted, the following relative URL should be called: 
    "/BrueckeService/seiltyp/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Seil columns: 
    - column: LaengeMeter 
    - column: Seiltyp 
    - column: Bruecke 
    - column: Seilsystem 
    - column: Beschreibung 
    - column: DurchmesserMillimeter 
The table should have the title "Seils" und the data must be loaded from the server with the following relative URL: 
    "/BrueckeService/seil/seiltyp/{id}"

4. The WasserlaufView must contain the following fields: 
    - name: Beschreibung   type: STRING 
    - name: Name   type: STRING 
    - name: Typ   type: STRING 
An existing Wasserlauf entity should be loaded from the relative URL: 
    "/BrueckeService/wasserlauf/{id}"   (HTTP-GET) 
If a new Wasserlauf entity has been created, the new entity should be posted to the relative URL: 
    "/BrueckeService/wasserlauf"   (HTTP-POST) 
If an existing Wasserlauf entity has been updated, the modified entity should be sent to the relative URL: 
    "/BrueckeService/wasserlauf/{id}"   (HTTP-PUT) 
If an existing Wasserlauf entity has to be deleted, the following relative URL should be called: 
    "/BrueckeService/wasserlauf/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Bruecke columns: 
    - column: BreiteMeter 
    - column: Name 
    - column: Eroeffnung 
    - column: Beschreibung 
    - column: LaengeMeter 
    - column: Baujahr 
    - column: Tragwerkssystem 
    - column: Wasserlauf 
    - column: BeweglichesBrueckensystem 
    - column: Material 
    - column: HauptspannweiteMeter 
    - column: IstBeweglich 
    - column: AnzahlFelder 
    - column: LichtraumhoeheMeter 
    - column: Ort 
The table should have the title "Brueckes" und the data must be loaded from the server with the following relative URL: 
    "/BrueckeService/bruecke/wasserlauf/{id}"