Prompt for the LandApp

Please create a React-JS application for the LandModule. The application  has to offer the following views for the user interface: 
    1. CarsharingVerbandView 
    2. LandView 
    3. NutzerView 
    4. RegulierungView 
    5. ZahlungsmethodeView 
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 CarsharingVerbandView must contain the following fields: 
    - name: Land   type: Land 
    - name: Name   type: STRING 
    - name: Webseite   type: STRING 
The data source for the [Land] select control should be loaded from the relative URL: 
    "/LandService/land"   (HTTP-GET) 
An existing CarsharingVerband entity should be loaded from the relative URL: 
    "/LandService/carsharingverband/{id}"   (HTTP-GET) 
If a new CarsharingVerband entity has been created, the new entity should be posted to the relative URL: 
    "/LandService/carsharingverband"   (HTTP-POST) 
If an existing CarsharingVerband entity has been updated, the modified entity should be sent to the relative URL: 
    "/LandService/carsharingverband/{id}"   (HTTP-PUT) 
If an existing CarsharingVerband entity has to be deleted, the following relative URL should be called: 
    "/LandService/carsharingverband/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Verbandsmitgliedschaft columns: 
    - column: Mitgliedsart 
    - column: CarsharingOrganisation 
    - column: MitgliedSeit 
    - column: CarsharingVerband 
The table should have the title "Verbandsmitgliedschafts" und the data must be loaded from the server with the following relative URL: 
    "/CarsharingOrganisationService/verbandsmitgliedschaft/carsharingverband/{id}"

2. The LandView must contain the following fields: 
    - name: IsoCode   type: STRING 
    - name: Name   type: STRING 
An existing Land entity should be loaded from the relative URL: 
    "/LandService/land/{id}"   (HTTP-GET) 
If a new Land entity has been created, the new entity should be posted to the relative URL: 
    "/LandService/land"   (HTTP-POST) 
If an existing Land entity has been updated, the modified entity should be sent to the relative URL: 
    "/LandService/land/{id}"   (HTTP-PUT) 
If an existing Land entity has to be deleted, the following relative URL should be called: 
    "/LandService/land/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Regulierung columns: 
    - column: GueltigAb 
    - column: Beschreibung 
    - column: Name 
    - column: Land 
The table should have the title "Regulierungs" und the data must be loaded from the server with the following relative URL: 
    "/LandService/regulierung/land/{id}" 
Add a HTML table to the view with the following OepnvBetreiber columns: 
    - column: Stadt 
    - column: Name 
    - column: Land 
    - column: Webseite 
The table should have the title "OepnvBetreibers" und the data must be loaded from the server with the following relative URL: 
    "/CarsharingOrganisationService/oepnvbetreiber/land/{id}" 
Add a HTML table to the view with the following Nutzer columns: 
    - column: Geburtsdatum 
    - column: Vorname 
    - column: MitgliedSeit 
    - column: FuehrerscheinLand 
    - column: FuehrerscheinNummer 
    - column: Email 
    - column: Telefonnummer 
    - column: Status 
    - column: Nachname 
The table should have the title "Nutzers" und the data must be loaded from the server with the following relative URL: 
    "/LandService/nutzer/fuehrerscheinland/{id}" 
Add a HTML table to the view with the following CarsharingVerband columns: 
    - column: Name 
    - column: Webseite 
    - column: Land 
The table should have the title "CarsharingVerbands" und the data must be loaded from the server with the following relative URL: 
    "/LandService/carsharingverband/land/{id}" 
Add a HTML table to the view with the following Stadt columns: 
    - column: Name 
    - column: Postleitzahl 
    - column: Region 
    - column: Land 
The table should have the title "Stadts" und the data must be loaded from the server with the following relative URL: 
    "/CarsharingOrganisationService/stadt/land/{id}"

3. The NutzerView must contain the following fields: 
    - name: Email   type: STRING 
    - name: FuehrerscheinLand   type: Land 
    - name: FuehrerscheinNummer   type: STRING 
    - name: Geburtsdatum   type: DATE 
    - name: MitgliedSeit   type: DATE 
    - name: Nachname   type: STRING 
    - name: Status   type: STRING 
    - name: Telefonnummer   type: STRING 
    - name: Vorname   type: STRING 
The data source for the [FuehrerscheinLand] select control should be loaded from the relative URL: 
    "/LandService/land"   (HTTP-GET) 
An existing Nutzer entity should be loaded from the relative URL: 
    "/LandService/nutzer/{id}"   (HTTP-GET) 
If a new Nutzer entity has been created, the new entity should be posted to the relative URL: 
    "/LandService/nutzer"   (HTTP-POST) 
If an existing Nutzer entity has been updated, the modified entity should be sent to the relative URL: 
    "/LandService/nutzer/{id}"   (HTTP-PUT) 
If an existing Nutzer entity has to be deleted, the following relative URL should be called: 
    "/LandService/nutzer/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Zahlungsmethode columns: 
    - column: Nutzer 
    - column: Anbieter 
    - column: MaskiertesKonto 
    - column: Standard 
    - column: Methode 
    - column: Ablaufdatum 
The table should have the title "Zahlungsmethodes" und the data must be loaded from the server with the following relative URL: 
    "/LandService/zahlungsmethode/nutzer/{id}" 
Add a HTML table to the view with the following Rechnung columns: 
    - column: Nutzer 
    - column: CarsharingOrganisation 
    - column: ZeitraumEnde 
    - column: Status 
    - column: Gesamtbetrag 
    - column: ZeitraumStart 
    - column: Rechnungsnummer 
    - column: AusgestelltAm 
The table should have the title "Rechnungs" und the data must be loaded from the server with the following relative URL: 
    "/RechnungService/rechnung/nutzer/{id}" 
Add a HTML table to the view with the following Mitgliedschaft columns: 
    - column: Mitgliedsnummer 
    - column: CarsharingOrganisation 
    - column: GastgeberAdresse 
    - column: Nutzer 
    - column: Enddatum 
    - column: Startdatum 
    - column: Gastgeber 
The table should have the title "Mitgliedschafts" und the data must be loaded from the server with the following relative URL: 
    "/StationService/mitgliedschaft/nutzer/{id}"

4. The RegulierungView must contain the following fields: 
    - name: Beschreibung   type: STRING 
    - name: GueltigAb   type: DATE 
    - name: Land   type: Land 
    - name: Name   type: STRING 
The data source for the [Land] select control should be loaded from the relative URL: 
    "/LandService/land"   (HTTP-GET) 
An existing Regulierung entity should be loaded from the relative URL: 
    "/LandService/regulierung/{id}"   (HTTP-GET) 
If a new Regulierung entity has been created, the new entity should be posted to the relative URL: 
    "/LandService/regulierung"   (HTTP-POST) 
If an existing Regulierung entity has been updated, the modified entity should be sent to the relative URL: 
    "/LandService/regulierung/{id}"   (HTTP-PUT) 
If an existing Regulierung entity has to be deleted, the following relative URL should be called: 
    "/LandService/regulierung/{id}"   (HTTP-DELETE)

5. The ZahlungsmethodeView must contain the following fields: 
    - name: Ablaufdatum   type: DATE 
    - name: Anbieter   type: STRING 
    - name: MaskiertesKonto   type: STRING 
    - name: Methode   type: STRING 
    - name: Nutzer   type: Nutzer 
    - name: Standard   type: BOOL 
The data source for the [Nutzer] select control should be loaded from the relative URL: 
    "/LandService/nutzer"   (HTTP-GET) 
An existing Zahlungsmethode entity should be loaded from the relative URL: 
    "/LandService/zahlungsmethode/{id}"   (HTTP-GET) 
If a new Zahlungsmethode entity has been created, the new entity should be posted to the relative URL: 
    "/LandService/zahlungsmethode"   (HTTP-POST) 
If an existing Zahlungsmethode entity has been updated, the modified entity should be sent to the relative URL: 
    "/LandService/zahlungsmethode/{id}"   (HTTP-PUT) 
If an existing Zahlungsmethode entity has to be deleted, the following relative URL should be called: 
    "/LandService/zahlungsmethode/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Zahlung columns: 
    - column: BezahltAm 
    - column: Transaktionsreferenz 
    - column: Betrag 
    - column: Zahlungsmethode 
    - column: Rechnung 
    - column: Status 
The table should have the title "Zahlungs" und the data must be loaded from the server with the following relative URL: 
    "/RechnungService/zahlung/zahlungsmethode/{id}"