Prompt for the KreuzungApp

Please create a React-JS application for the KreuzungModule. The application  has to offer the following views for the user interface: 
    1. DetektorView 
    2. GesetzView 
    3. KreuzungView 
    4. SteuerstrategieView 
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 DetektorView must contain the following fields: 
    - name: Detektortyp   type: STRING 
    - name: IstEinsatzfahrzeug   type: BOOL 
    - name: IstOeV   type: BOOL 
    - name: Kreuzung   type: Kreuzung 
    - name: Positionsbeschreibung   type: STRING 
    - name: Steuerstrategie   type: Steuerstrategie 
    - name: Verkehrsart   type: Verkehrsart 
The data source for the [Verkehrsart] select control should be loaded from the relative URL: 
    "/VerkehrsartService/verkehrsart"   (HTTP-GET) 
The data source for the [Kreuzung] select control should be loaded from the relative URL: 
    "/KreuzungService/kreuzung"   (HTTP-GET) 
The data source for the [Steuerstrategie] select control should be loaded from the relative URL: 
    "/KreuzungService/steuerstrategie"   (HTTP-GET) 
An existing Detektor entity should be loaded from the relative URL: 
    "/KreuzungService/detektor/{id}"   (HTTP-GET) 
If a new Detektor entity has been created, the new entity should be posted to the relative URL: 
    "/KreuzungService/detektor"   (HTTP-POST) 
If an existing Detektor entity has been updated, the modified entity should be sent to the relative URL: 
    "/KreuzungService/detektor/{id}"   (HTTP-PUT) 
If an existing Detektor entity has to be deleted, the following relative URL should be called: 
    "/KreuzungService/detektor/{id}"   (HTTP-DELETE)

2. The GesetzView must contain the following fields: 
    - name: Beschreibung   type: STRING 
    - name: Land   type: Land 
    - name: Name   type: STRING 
    - name: Paragraph   type: STRING 
The data source for the [Land] select control should be loaded from the relative URL: 
    "/LandService/land"   (HTTP-GET) 
An existing Gesetz entity should be loaded from the relative URL: 
    "/KreuzungService/gesetz/{id}"   (HTTP-GET) 
If a new Gesetz entity has been created, the new entity should be posted to the relative URL: 
    "/KreuzungService/gesetz"   (HTTP-POST) 
If an existing Gesetz entity has been updated, the modified entity should be sent to the relative URL: 
    "/KreuzungService/gesetz/{id}"   (HTTP-PUT) 
If an existing Gesetz entity has to be deleted, the following relative URL should be called: 
    "/KreuzungService/gesetz/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following GesetzlicheBezeichnung columns: 
    - column: Gesetz 
    - column: Beschreibung 
    - column: SignalSystem 
    - column: Land 
    - column: Name 
The table should have the title "GesetzlicheBezeichnungs" und the data must be loaded from the server with the following relative URL: 
    "/LandService/gesetzlichebezeichnung/gesetz/{id}" 
Add a HTML table to the view with the following SignalSystem columns: 
    - column: Name 
    - column: GesetzlicheBezeichnung 
    - column: StandardBezeichnung 
    - column: Beschreibung 
    - column: Land 
    - column: Gesetz 
The table should have the title "SignalSystems" und the data must be loaded from the server with the following relative URL: 
    "/SignalSystemService/signalsystem/gesetz/{id}"

3. The KreuzungView must contain the following fields: 
    - name: AnzahlArme   type: LONG 
    - name: Breitengrad   type: STRING 
    - name: HatBusspur   type: BOOL 
    - name: HatFussgaengerueberwege   type: BOOL 
    - name: HatRadueberwege   type: BOOL 
    - name: HatTram   type: BOOL 
    - name: IstKreisverkehrMoeglich   type: BOOL 
    - name: Laengengrad   type: STRING 
    - name: Land   type: Land 
    - name: Name   type: STRING 
    - name: Stadt   type: STRING 
The data source for the [Land] select control should be loaded from the relative URL: 
    "/LandService/land"   (HTTP-GET) 
An existing Kreuzung entity should be loaded from the relative URL: 
    "/KreuzungService/kreuzung/{id}"   (HTTP-GET) 
If a new Kreuzung entity has been created, the new entity should be posted to the relative URL: 
    "/KreuzungService/kreuzung"   (HTTP-POST) 
If an existing Kreuzung entity has been updated, the modified entity should be sent to the relative URL: 
    "/KreuzungService/kreuzung/{id}"   (HTTP-PUT) 
If an existing Kreuzung entity has to be deleted, the following relative URL should be called: 
    "/KreuzungService/kreuzung/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following SignalInstallation columns: 
    - column: Beschreibung 
    - column: Eigentuemertyp 
    - column: Kreuzung 
    - column: Name 
    - column: Installationsdatum 
    - column: IstStationaer 
    - column: Einsatzkontext 
    - column: IstMobil 
The table should have the title "SignalInstallations" und the data must be loaded from the server with the following relative URL: 
    "/SignalInstallationService/signalinstallation/kreuzung/{id}" 
Add a HTML table to the view with the following Signalgruppe columns: 
    - column: IstFahrzeuggruppe 
    - column: Verkehrsart 
    - column: IstFussgaengergruppe 
    - column: Kreuzung 
    - column: Name 
    - column: IstOeVGruppe 
    - column: Beschreibung 
    - column: IstRadgruppe 
The table should have the title "Signalgruppes" und the data must be loaded from the server with the following relative URL: 
    "/VerkehrsartService/signalgruppe/kreuzung/{id}" 
Add a HTML table to the view with the following Programmplan columns: 
    - column: Tagtyp 
    - column: Endzeit 
    - column: Steuerstrategie 
    - column: Kreuzung 
    - column: Beschreibung 
    - column: Startzeit 
    - column: Name 
    - column: Zykluszeit 
The table should have the title "Programmplans" und the data must be loaded from the server with the following relative URL: 
    "/SignalSymbolService/programmplan/kreuzung/{id}" 
Add a HTML table to the view with the following OeVPriorisierung columns: 
    - column: Verkehrsart 
    - column: Kreuzung 
    - column: Beschreibung 
    - column: Detektionsmethode 
    - column: Priorisierungsart 
The table should have the title "OeVPriorisierungs" und the data must be loaded from the server with the following relative URL: 
    "/VerkehrsartService/oevpriorisierung/kreuzung/{id}" 
Add a HTML table to the view with the following Zufahrt columns: 
    - column: GeschwindigkeitslimitKmh 
    - column: Kreuzung 
    - column: Richtung 
    - column: AnzahlFahrstreifen 
    - column: Beschreibung 
    - column: HatBusspur 
    - column: HatTramgleis 
The table should have the title "Zufahrts" und the data must be loaded from the server with the following relative URL: 
    "/SignalSystemService/zufahrt/kreuzung/{id}" 
Add a HTML table to the view with the following Ueberweg columns: 
    - column: Typ 
    - column: HatZebrastreifen 
    - column: Kreuzung 
    - column: IstEbenerdig 
    - column: Beschreibung 
    - column: IstSignalisiert 
The table should have the title "Ueberwegs" und the data must be loaded from the server with the following relative URL: 
    "/SignalFarbeService/ueberweg/kreuzung/{id}" 
Add a HTML table to the view with the following Detektor columns: 
    - column: Detektortyp 
    - column: IstOeV 
    - column: Kreuzung 
    - column: Verkehrsart 
    - column: Positionsbeschreibung 
    - column: IstEinsatzfahrzeug 
    - column: Steuerstrategie 
The table should have the title "Detektors" und the data must be loaded from the server with the following relative URL: 
    "/KreuzungService/detektor/kreuzung/{id}"

4. The SteuerstrategieView must contain the following fields: 
    - name: Beschreibung   type: STRING 
    - name: IstFestzeit   type: BOOL 
    - name: IstKoordiniert   type: BOOL 
    - name: IstVerkehrsabhaengig   type: BOOL 
    - name: Name   type: STRING 
    - name: ZykluszeitMax   type: LONG 
    - name: ZykluszeitMin   type: LONG 
An existing Steuerstrategie entity should be loaded from the relative URL: 
    "/KreuzungService/steuerstrategie/{id}"   (HTTP-GET) 
If a new Steuerstrategie entity has been created, the new entity should be posted to the relative URL: 
    "/KreuzungService/steuerstrategie"   (HTTP-POST) 
If an existing Steuerstrategie entity has been updated, the modified entity should be sent to the relative URL: 
    "/KreuzungService/steuerstrategie/{id}"   (HTTP-PUT) 
If an existing Steuerstrategie entity has to be deleted, the following relative URL should be called: 
    "/KreuzungService/steuerstrategie/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Programmplan columns: 
    - column: Tagtyp 
    - column: Endzeit 
    - column: Steuerstrategie 
    - column: Kreuzung 
    - column: Beschreibung 
    - column: Startzeit 
    - column: Name 
    - column: Zykluszeit 
The table should have the title "Programmplans" und the data must be loaded from the server with the following relative URL: 
    "/SignalSymbolService/programmplan/steuerstrategie/{id}" 
Add a HTML table to the view with the following Detektor columns: 
    - column: Detektortyp 
    - column: IstOeV 
    - column: Kreuzung 
    - column: Verkehrsart 
    - column: Positionsbeschreibung 
    - column: IstEinsatzfahrzeug 
    - column: Steuerstrategie 
The table should have the title "Detektors" und the data must be loaded from the server with the following relative URL: 
    "/KreuzungService/detektor/steuerstrategie/{id}"