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. FoerderprogrammView 
    2. LandView 
    3. VereinsregisterView 
The views have to be reachable for the user via a menu list at the left side of each view. The requirements for the 3 views are defined below.

1. The FoerderprogrammView must contain the following fields: 
    - name: Beschreibung   type: STRING 
    - name: Land   type: Land 
    - name: Name   type: STRING 
    - name: Traeger   type: STRING 
The data source for the [Land] select control should be loaded from the relative URL: 
    "/LandService/land"   (HTTP-GET) 
An existing Foerderprogramm entity should be loaded from the relative URL: 
    "/LandService/foerderprogramm/{id}"   (HTTP-GET) 
If a new Foerderprogramm entity has been created, the new entity should be posted to the relative URL: 
    "/LandService/foerderprogramm"   (HTTP-POST) 
If an existing Foerderprogramm entity has been updated, the modified entity should be sent to the relative URL: 
    "/LandService/foerderprogramm/{id}"   (HTTP-PUT) 
If an existing Foerderprogramm entity has to be deleted, the following relative URL should be called: 
    "/LandService/foerderprogramm/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Foerderentscheidung columns: 
    - column: IstAusBeendetemVerfahren 
    - column: Foerderprogramm 
    - column: Betrag 
    - column: Gericht 
    - column: Begruendung 
    - column: Datum 
    - column: Verein 
    - column: Waehrung 
The table should have the title "Foerderentscheidungs" und the data must be loaded from the server with the following relative URL: 
    "/GerichtService/foerderentscheidung/foerderprogramm/{id}"

2. The LandView must contain the following fields: 
    - name: AmtlicherName   type: STRING 
    - name: IsoCode   type: STRING 
    - name: Name   type: STRING 
    - name: Region   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 Gericht columns: 
    - column: Ort 
    - column: Land 
    - column: Name 
    - column: IstRegistergericht 
The table should have the title "Gerichts" und the data must be loaded from the server with the following relative URL: 
    "/GerichtService/gericht/land/{id}" 
Add a HTML table to the view with the following Mitglied columns: 
    - column: Nachname 
    - column: Geschlecht 
    - column: Geburtsdatum 
    - column: IstMinderjaehrig 
    - column: Staatsangehoerigkeit 
    - column: Vorname 
The table should have the title "Mitglieds" und the data must be loaded from the server with the following relative URL: 
    "/MitgliedService/mitglied/staatsangehoerigkeit/{id}" 
Add a HTML table to the view with the following Gesetz columns: 
    - column: GueltigVon 
    - column: Zitierweise 
    - column: Land 
    - column: Titel 
    - column: Gesetzestyp 
    - column: Kurztitel 
    - column: GueltigBis 
    - column: Beschreibung 
The table should have the title "Gesetzs" und the data must be loaded from the server with the following relative URL: 
    "/GesetzService/gesetz/land/{id}" 
Add a HTML table to the view with the following Vereinsregister columns: 
    - column: Land 
    - column: Name 
    - column: SeitJahr 
    - column: Registergericht 
    - column: IstElektronisch 
The table should have the title "Vereinsregisters" und the data must be loaded from the server with the following relative URL: 
    "/LandService/vereinsregister/land/{id}" 
Add a HTML table to the view with the following Foerderprogramm columns: 
    - column: Beschreibung 
    - column: Land 
    - column: Traeger 
    - column: Name 
The table should have the title "Foerderprogramms" und the data must be loaded from the server with the following relative URL: 
    "/LandService/foerderprogramm/land/{id}" 
Add a HTML table to the view with the following Verein columns: 
    - column: Oberverein 
    - column: Zweckbeschreibung 
    - column: Register 
    - column: IstMildtaetig 
    - column: Aufloesungsdatum 
    - column: SatzungUrl 
    - column: IstPolitisch 
    - column: IstKirchlich 
    - column: IstSportlich 
    - column: IstInternational 
    - column: IstDachverband 
    - column: Registernummer 
    - column: SitzPlz 
    - column: Kurzname 
    - column: IstEingetragen 
    - column: SitzAdresse 
    - column: IstGemeinnuetzig 
    - column: Name 
    - column: Rechtsform 
    - column: Gruendungsdatum 
    - column: Land 
    - column: SitzOrt 
The table should have the title "Vereins" und the data must be loaded from the server with the following relative URL: 
    "/VereinService/verein/land/{id}"

3. The VereinsregisterView must contain the following fields: 
    - name: IstElektronisch   type: BOOL 
    - name: Land   type: Land 
    - name: Name   type: STRING 
    - name: Registergericht   type: Gericht 
    - name: SeitJahr   type: INT 
The data source for the [Registergericht] select control should be loaded from the relative URL: 
    "/GerichtService/gericht"   (HTTP-GET) 
The data source for the [Land] select control should be loaded from the relative URL: 
    "/LandService/land"   (HTTP-GET) 
An existing Vereinsregister entity should be loaded from the relative URL: 
    "/LandService/vereinsregister/{id}"   (HTTP-GET) 
If a new Vereinsregister entity has been created, the new entity should be posted to the relative URL: 
    "/LandService/vereinsregister"   (HTTP-POST) 
If an existing Vereinsregister entity has been updated, the modified entity should be sent to the relative URL: 
    "/LandService/vereinsregister/{id}"   (HTTP-PUT) 
If an existing Vereinsregister entity has to be deleted, the following relative URL should be called: 
    "/LandService/vereinsregister/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Verein columns: 
    - column: Oberverein 
    - column: Zweckbeschreibung 
    - column: Register 
    - column: IstMildtaetig 
    - column: Aufloesungsdatum 
    - column: SatzungUrl 
    - column: IstPolitisch 
    - column: IstKirchlich 
    - column: IstSportlich 
    - column: IstInternational 
    - column: IstDachverband 
    - column: Registernummer 
    - column: SitzPlz 
    - column: Kurzname 
    - column: IstEingetragen 
    - column: SitzAdresse 
    - column: IstGemeinnuetzig 
    - column: Name 
    - column: Rechtsform 
    - column: Gruendungsdatum 
    - column: Land 
    - column: SitzOrt 
The table should have the title "Vereins" und the data must be loaded from the server with the following relative URL: 
    "/VereinService/verein/register/{id}"